[konsole] [Bug 371919] export COLORTERM=truecolor

[Egmont Koblinger]

https://bugs.kde.org/show_bug.cgi?id=371919

Egmont Koblinger <egmont at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #5 from Egmont Koblinger <egmont at gmail.com> ---
Thanks for your patch! Reopening for some more discussion:

Your patch just made me realize that konsole doesn't even advertise 256-color
support (TERM is set to xterm rather than xterm-256color).

With this patch, it still doesn't advertise support for the pretty widespread
256-color feature, yet it advertises the less common true colors. This doesn't
make too much sense to me. S-lang also seems to obey these pieces of
information, and refuses to use the 256-color palette, yet allows true colors.

Strictly speaking, these are two orthogonal features, and theoretically there
could exist a terminal emulator that supports RGB but not the 256-color palette
(although I'd be really surprised if it turned out that there
exists/existed/will ever exist one). So one can kinda defend this behavior, we
could leave konsole as-is, and I could modify the Midnight Commander patch
accordingly.

In practice, since the true color feature is getting more and more popular
because 256 colors is not enough for some people, I'd say it's more practical
to think about it as the true color being something that might be implemented,
but only after you've got the 256-color palette anyways. MC's current
implementation also does this, it has a sanity check for 256-color support
according to terminfo before allowing true colors subject to COLORTERM, and
it's expected that if a skin definition mentions the usage of true colors then
256-colors are allowed too.

So the question is: Which direction do you think is the better?

Have you already considered, or could you please consider switching the default
to xterm-256color? That would simplify this situation a lot, actually we could
just ignore this problem. Has this perhaps been already discussed and rejected
for a reason? I found bug 212145 which seems to got forgotten, maybe time to
revive? (Just FYI: gnome-terminal changed the default to xterm-256color in
vte-0.40, released in March 2015.)

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.