After many months, this finally got fixed. Two of my systems (with less emerged in late July of this year) have a working lesspipe.sh. Somebody decided to break it again, so it no longer works correctly. /usr/portage/sys-apps/less/files/lesspipe.sh Reproducible: Always Steps to Reproduce: 1. less /var/log/messages.1.gz 2. "/var/log/messages.1.gz" may be a binary file. See it anyway? 3. binary garbage Expected Results: See the uncompressed log file.
Created attachment 70778 [details] Working lesspipe.sh from about 20050725
the problem is that messages.1.gz used to fall down into the manpage case and would be shown as text ... but it would also catch something like libc.so.6.gz and incorrectly display it as binary data so any files which are matched as '*.[0-9].gz' and are not of file type 'troff' are pretty much ignored
fixed in cvs
