Summary: | sys-apps/less default rich processing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tobias Klausmann (RETIRED) <klausman> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | ray |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tobias Klausmann (RETIRED)
![]() LESSOPEN has *always* been enabled if you want it off, just do: # echo 'LESSOPEN=""' > /etc/env.d/99local # env-update Well, if it was always enabled, why haven't I ever noticed this behaviour before?! Some goes for a colleague who runs his own machine which I don't even have an account on. I can hardly believe that I never ever triggered this behaviour before (and neither did he). Maybe the permissions of lesspipe.sh changed. What does CVS say wrt changes to env.d/00basic? you're assuming the wrong thing lesspipe.sh itself has increased in terms of features, read the source Ah, well, that explains it of course. Thanks for your time. *** Bug 179411 has been marked as a duplicate of this bug. *** |