Please set LESSCOLOR=yes as default in /etc/env.d/70less or add an information notice to the ebuild so the users can easily find how to switch this on or off. Thanks.
`lesspipe.sh --help` already clearly documents things defaulting to on is not acceptable -- see Bug 188835 exactly as referenced in the colorization code already
I had no idea such a thing as lesspipe.sh existed. I wonder how many users do. Correct me if I am mistaken on this, but I'm quite sure that syntax highlighting was enabled out of the box in the past. Perhaps I just didn't notice, but I still think that it's important to notify users about such changed behaviour. Regardless of bug 188835, many users may still want syntax highlighting with less. I think it would do good (happier users) to make the trivial change of adding a few lines to the ebuild stating how to enable syntax highlighting, e.g. elog "Syntax highlighting is disabled by default, because it may take a long time for big files (bug #188835). If you still want to enable syntax highlighting for your user, add the following line to your ~/.bash_profile" elog " " elog " export LESSCOLOR=yes" elog " " elog "To enable syntax highlighting for all users, add the following line to /etc/env.d/70less" elog " " elog " LESSCOLOR=yes" All I ask is to take this under consideration. Thanks.
the ebuild now suggests people run `lesspipe -h` for color info. i dont want to duplicate this info in the ebuilds and the script itself.
Perhaps it were a better idea to instruct people to install a separate syntax highlighter (e.g. app-text/highlight) and add something like the following to their environment to get highlighting: LESSCOLOR=yes LESSCOLORIZER=highlight
