256/24-bit colors outside bottom region / coloring breaks after view change

[jonathanslenders]

Hi @Maximus5,

What is the reason that we can only have 256 colors in the bottom region?

I'm the author of ptpython, a Python REPL, and working on better integration with ConEmu. We'd like to have 256 colors, similar to all VT100 terminals. But it doesn't make sense to scroll to the bottom. A REPL should be shown at the current position, right below the output of the previous command. It's also not a full-screen application.

Maybe, there is something that I'm missing. But xterm, gnome-terminal, etc... all manage to display the 256 colors for the whole console.

An alternative would be to make ConEmu already scroll to the bottom region in its initialization script that runs when creating a new console, but that's rather ugly. (I don't expect every user to change anything there.)

Jonathan

[Maximus5]

Due to historical reasons (true color was implement by contributor for use with Far Manager) it available for "visible part of the buffer", the bottom part is a working area of Far Manager.

I completely understand the lack of implementation, but it's hard to implement seamless synchronization of windows RealConsole surface with virtual ConEmu true color surface. Almost all parts of sources related to console services must be refactored or even rewritten from the scratch.

https://conemu.github.io/en/AnsiEscapeCodes.html#xterm_256_color_processing_requirements

[markonop93]

hello @Maximus5
im not following what i have to do to enable support of colors now
i try to use clink with sgr 35;5;200 color and it works on regular cmd.exe and not in conemu

i have enabled "ConEmuHk inject", "ANSI and xterm sequences" and "TrueMod (24bit color) support"
i run regular/admin cmd.exe through clink and no color
im not sure how to completely disable scroll and if this is possible now or whats this issue is about
however color is not available also on bottom of console where i input