Jeff King [off-list ref] writes:
On Wed, Sep 22, 2021 at 10:21:22PM -0700, The Grey Wolf wrote:
quoted
Anything else you want to add:
I searched google and the documentation as best I was able for
this, but I am unable to find anywhere that will let me disable
(or enable) colour for a particular term type. Sometimes I'm on
an xterm, for which this is GREAT. Sometimes I'm on a Wyse WY60,
for which this is sub-optimal. My workaround is to disable colour
completely, which is reluctantly acceptable, but it would be nice
to say "If I'm on an xterm/aterm/urxvt/ansi terminal, enable
colour or cursor-positioning, otherwise shut it off." If this
seems too much of a one-off to handle, fine, but most things that
talk fancy to screens are kind enough to allow an opt-out based on
terminal type. :)
Git doesn't have any kind of list of terminals, beyond knowing that
"dumb" should disable auto-color. It's possible we could expand that if
there are known terminals that don't understand ANSI colors. I'm a bit
wary of having a laundry list of obscure terminals, though.
If we built against ncurses or some other terminfo-aware library we
could outsource that, but that would be a new dependency. I'm hesitant
to do that even as an optional dependency given the bang-for-the-buck
(and certainly making it require would be right out).
I was wondering if Gray Wolf can run screen on the Wyse, and then
wouldn't git see TERM=screen which is pretty much ANSI if I am not
mistaken ;-)?
On September 23, 2021 5:55 PM, Junio C Hamano wrote:
Jeff King [off-list ref] writes:
quoted
On Wed, Sep 22, 2021 at 10:21:22PM -0700, The Grey Wolf wrote:
quoted
Anything else you want to add:
I searched google and the documentation as best I was able for
this, but I am unable to find anywhere that will let me disable
(or enable) colour for a particular term type. Sometimes I'm on
an xterm, for which this is GREAT. Sometimes I'm on a Wyse WY60,
for which this is sub-optimal. My workaround is to disable colour
completely, which is reluctantly acceptable, but it would be nice
to say "If I'm on an xterm/aterm/urxvt/ansi terminal, enable
colour or cursor-positioning, otherwise shut it off." If this
seems too much of a one-off to handle, fine, but most things that
talk fancy to screens are kind enough to allow an opt-out based on
terminal type. :)
Git doesn't have any kind of list of terminals, beyond knowing that
"dumb" should disable auto-color. It's possible we could expand that
if there are known terminals that don't understand ANSI colors. I'm a
bit wary of having a laundry list of obscure terminals, though.
If we built against ncurses or some other terminfo-aware library we
could outsource that, but that would be a new dependency. I'm hesitant
to do that even as an optional dependency given the bang-for-the-buck
(and certainly making it require would be right out).
I was wondering if Gray Wolf can run screen on the Wyse, and then wouldn't git see TERM=screen which is pretty much ANSI if I am
not
mistaken ;-)?
Would something like switch in .gitconfig make a difference? Like core.colourize=false. There are situations where SSH sessions come
in from automation, like Jenkins and Travis, which sets term to something other than dumb by default. Coloring makes a mess of the
output. The ability to turn off colouring off by user might be helpful.
-Randall
On Thu, Sep 23, 2021 at 06:04:20PM -0400, Randall S. Becker wrote:
On September 23, 2021 5:55 PM, Junio C Hamano wrote:
quoted
Jeff King [off-list ref] writes:
quoted
On Wed, Sep 22, 2021 at 10:21:22PM -0700, The Grey Wolf wrote:
quoted
Anything else you want to add:
I searched google and the documentation as best I was able for
this, but I am unable to find anywhere that will let me disable
(or enable) colour for a particular term type. Sometimes I'm on
an xterm, for which this is GREAT. Sometimes I'm on a Wyse WY60,
for which this is sub-optimal. My workaround is to disable colour
completely, which is reluctantly acceptable, but it would be nice
to say "If I'm on an xterm/aterm/urxvt/ansi terminal, enable
colour or cursor-positioning, otherwise shut it off." If this
seems too much of a one-off to handle, fine, but most things that
talk fancy to screens are kind enough to allow an opt-out based on
terminal type. :)
Git doesn't have any kind of list of terminals, beyond knowing that
"dumb" should disable auto-color. It's possible we could expand that
if there are known terminals that don't understand ANSI colors. I'm a
bit wary of having a laundry list of obscure terminals, though.
If we built against ncurses or some other terminfo-aware library we
could outsource that, but that would be a new dependency. I'm hesitant
to do that even as an optional dependency given the bang-for-the-buck
(and certainly making it require would be right out).
I was wondering if Gray Wolf can run screen on the Wyse, and then wouldn't git see TERM=screen which is pretty much ANSI if I am
not
quoted
mistaken ;-)?
Would something like switch in .gitconfig make a difference? Like core.colourize=false. There are situations where SSH sessions come
in from automation, like Jenkins and Travis, which sets term to something other than dumb by default. Coloring makes a mess of the
output. The ability to turn off colouring off by user might be helpful.
-Randall
That already exists: `color.ui`:
This variable determines the default value for variables such as
color.diff and color.grep that control the use of color per command
family.
[..]
Set it to false or never if you prefer Git commands not to use color
unless enabled explicitly with some other configuration or the --color
option.
Kevin