Hi, could you please fix the 'zless' bug described. 'less' ver. 451 log; Use exit code of LESSOPEN script if LESSOPEN starts with "||".
Thanks, jb ---------- Forwarded message ---------- From: Mark Nudelman <ma...@greenwoodsoftware.com> Date: Mon, Sep 8, 2014 at 5:54 PM Subject: Re: 'less' bug report To: J B <jb.1234a...@gmail.com> Hi jb, This was fixed in less-451 with the introduction of the double pipe syntax in LESSOPEN. It requires your lessopen script to return the appropriate exit code. --Mark On 9/8/2014 7:31 AM, J B wrote: > Hi, > this is a bug report for 'less' entry. > > $ touch empty.txt > $ less empty.txt > empty.txt (END) > $ gzip empty.txt > $ zless empty.txt.gz > "empty.txt.gz" may be a binary file. See it anyway? > > The last response should be as for 'less empty.txt'. > According to Peter Selinger, author of ccrypt utilities: > "The problem is that less, when using an input filter, regards an empty > file > as a condition indicating "filtering unsuccessful", and will just show > the unfiltered file instead." > This 'less' behavior causes a problem for other utilities as well. > > jb >
