On 14/02/2022 23:36, Arsen Arsenović wrote:
[ Reposting since I didn't reply-all the first time; apologies ]
Your change could break this setup if there were
entries in "specific config" that weren't overridden later,
and even if they were, it would result in larger LS_COLORS env vars.
Ah, I
[ Reposting since I didn't reply-all the first time; apologies ]
> Your change could break this setup if there were
> entries in "specific config" that weren't overridden later,
> and even if they were, it would result in larger LS_COLORS env vars.
Ah, I see. I lacked a full understanding of this
On 12/02/2022 21:54, Arsen Arsenović wrote:
COLORTERM is an environment used usually to expose truecolor support in
terminal emulators. If a terminal emulator supports truecolor, it is
surely reasonable to assume it also supports 8/16/256 colors.
This implicitly supports foot, alacritty and any
On 22/02/13 14:15, Pádraig Brady wrote:
> Though it was pointed out that COLORTERM may not be preserved across ssh etc.
> Now doing this would be no worse, so I'm inclined to apply this.
I could follow up with OpenSSH at some point, too, to include $COLORTERM
in the default environment set.
On 12/02/2022 21:54, Arsen Arsenović wrote:
COLORTERM is an environment used usually to expose truecolor support in
terminal emulators. If a terminal emulator supports truecolor, it is
surely reasonable to assume it also supports 8/16/256 colors.
This implicitly supports foot, alacritty and any
