RE: How dow we educate our users to configure less?

> >I'm saying the **opposite**. I'm saying this should be done in builtin/help.c *not* .profile.
> >
> >> Admittedly, I am in a highly complex situation, but it is a real one
> >> (ok, two because of a diverged path between NonStop and MVS) and there
> >> are hundreds in a similar situation.
> >
> >My patch [1] should work in all your environments.
> 
> Your patch will work in the environments but not in the use case I
> tried to explain. I do not want a single configuration of less colours
> in .git/config or ~/.gitconfig. That is not going to work in my
> situation. I have multiple less colour values that would apply within
> a given arbitrary timeframe. The configuration depends on the specific
> terminal type set in the environment, either dumb, vt220, t653x,
> xterm, cygwin, all of which may happy in short succession. I do not
> expect it to be practical to change my git settings to conform to this
> patch, so I am trying to point out that I do not see how it can solve
> my issue.

> The current support, using the TERM environment variable, which is
> passed to git in all situations either by the system itself on through
> scripts as is the case with Jenkins, is mostly sufficient for less and
> git to find its appropriate termcap on all platforms that I use on an
> ongoing basis (Windows Cygwin, NonStop OSS, NonStop GUARDIAN, Ubuntu,
> MacOS, MVS, USS, Jenkins). The NonStop GUARDIAN environment does
> present some paging issues that do not work correctly in some cases
> with some terminal emulators, but that's the emulator's problem, not
> the termcap specifically.
> 
> So what am I missing?