Date: Mon, 12 Nov 2007 17:51:36 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= <des@des.no>, Chuck Robey <chuckr@chuckr.org> Subject: Re: a better lesskey helper Message-ID: <200711121751.37051.jhb@freebsd.org> In-Reply-To: <868x57jfti.fsf@ds4.des.no> References: <4733AA45.6030905@chuckr.org> <4734C440.4070100@chuckr.org> <868x57jfti.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 09 November 2007 03:59:21 pm Dag-Erling Sm=C3=B8rgrav wrote: > Chuck Robey <chuckr@chuckr.org> writes: > > Dag-Erling Sm=C3=B8rgrav wrote: > >> Nikolay Pavlov <qpadla@gmail.com> writes: > >>> There is already such a file there. You just need to proper set an > >>> environment: setenv LESSOPEN '|lesspipe.sh %s' > >> zless will do that for you. > > Now I'm getting a bit confused. I know you from long before, and I > > know you wouldn't make mistakes easily. MY zless here doesn't decode > > executables and libs, but there's no man page, and zless --help gives > > only the standard less help info, so I don;'t know what zless does > > that less didn't do before I changed out the lesspipe.sh on my local > > system. >=20 > "that" refers to Nikolay's setenv trick. If you actually define > LESSOPEN in your environment, less will always use it, which may not be > what you want; instead, you can use less when you want to see the actual > file and zless when you want it "decoded". less -L =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200711121751.37051.jhb>