Date: Sat, 10 Nov 2007 16:26:24 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Chuck Robey <chuckr@chuckr.org> Cc: bv@wjv.com, freebsd-current@freebsd.org Subject: Re: a better lesskey helper Message-ID: <86hcjuglzz.fsf@ds4.des.no> In-Reply-To: <4734EA16.5090800@chuckr.org> (Chuck Robey's message of "Fri\, 09 Nov 2007 18\:15\:34 -0500") References: <20071109222421.037E116A494@hub.freebsd.org> <20071109224531.GA58036@wjv.com> <4734EA16.5090800@chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey <chuckr@chuckr.org> writes: > That sort of behavior is (I think, I haven't yet checked most) what I > am suggesting be brought into less. Look, let me repeat, now that I > have gotten confirmation that I wasn't wrong (thanks to Carl). It's > this: > > 1: modify our lesspipe.sh, so that, in addition to the detection of > various tar archives (along with compression), it also detects various > elf images, and uses objdump to display the info. Less will keep the > current behavior on any other binaries it hits, only decoding the elf > images. > > 2) add 1 line to our /etc/csh.cshrc and /etc/profile (to cover those > sh and csh compatible shells) so that the lesspipe.sh functionality no > longer needs folks to remember zless. I don't think it's needed, but > if users ask for it, it would be trivial to code up a variable, like > LESS_WITHOUT_LESSPIPE, that if defined could even block out these > changes. I can't see why folks would not want it, but I'm not fanatic > over it. > > 3) remove zless. None of that will happen. You are free to use your own lesspipe.sh on your own system, or install sysutils/most from ports, but the base system's lesspipe.sh will not change, LESSOPEN will not be defined in the default environment, and zless will stay. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86hcjuglzz.fsf>