Re: Deleting uncompressed Info/Doc files at upgrades
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "warp" == warp <warp@whitestar.soark.net> writes:
warp> --OwLcNYc0lM97+oe1
warp> Content-Type: text/plain; charset=us-ascii
warp> Content-Transfer-Encoding: quoted-printable
warp> On Thu, Oct 15, 1998 at 05:31:10PM -0400, Michael Stone wrote:
warp> <snip>
>> Hmm. We have zless to less gz'd files.
warp> zless nothing, a simple lesspipe.sh works great, for bigger stuff a not
warp> so simple lesspipe.sh (Can give a real complete one if you want, its
warp> what I use) works GREAT...
warp> Gives file listings for .tar's, handles .bz2 and .gz compression on a
warp> file transparently, gives nice readouts for .deb's and .rpm's, renders
warp> groffs (man pages), and transparently handles uuencoded files (under
warp> =2Euxx, .uux, and .uue)=20
warp> And its designed in such a way that something like
warp> less foo.tar.gz.uue.bz2.uue.gz
warp> works perfectly.. (=3D:]
warp> </plug>
Is this packaged? Could it be? Could you (at least) send it to me?
I'm still running bo, so if this compressed docs mess is fixed (yes,
fixed) in 2.0, fine.
BTW: my gv does not read compressed .ps files... but some people said
it would. How do I make it? (Or is this only in hamm?)
Bye, J
- --
Jürgen A. Erhard eMail: jae@laden.ilk.de phone: (GERMANY) 0721 27326
MARS: http://members.tripod.com/~Juergen_Erhard/mars_index.html
Debian GNU/Linux (http://www.debian.org)
"Windows NT" is an acronym for "Windows? No thanks." -- Russ McManus
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQEVAwUBNi+24QIG66LugGzRAQHdewf/fJ7L6Osrog9a1GsJ1JBdiPPNCgJmuTHF
eJNljYhRe6mbyRc1535LWFH2UGSd4UKJsSNao3FEEYKFGyrCfFANYNSFQn8sr74O
0Puxi0LP8DuOVpFUtqAkUKJg6E5UuiFtlJh6kKsesvxNeU1TsMH891Wkt4f7HzV7
zFoJmBIEZzxnIRDFpTMqhTw4ThHZlYSZ9KLsXoLda0qc/fs1vOCB5eGy3MoR2Edz
/Ot1L3VJa340oPZ+N6V+nyjQrakAzPUAlIm60Su2NCP3i/viFBLfhVIJzSZA81NU
92V41XQ+aK8+E4tDsnPUV9QkznKV6dCik4eo8zKlNhEwN4px2CT0zg==vKT7
-----END PGP SIGNATURE-----
Reply to: