Re: a better lesskey helper



Chuck Robey <chuckr@xxxxxxxxxx> 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
--
Dag-Erling Smørgrav - des@xxxxxx
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: a better lesskey helper
    ... elf images, and uses objdump to display the info.  Less will keep the ... longer needs folks to remember zless. ...
    (freebsd-current)
  • Re: a better lesskey helper
    ... MY zless here doesn't decode ... LESSOPEN in your environment, less will always use it, which may not be ... I have ocaisonally been surprised that a file was binary, but files that are binary, AND not elf encoded images, will still show up just like the current less without the objdump encoding I'm suggesting, no changes. ... It's only the elf images that get routed thru objdump ... ...
    (freebsd-current)