Open stevefolly opened 7 years ago
It has no sense unfortunately. The bottle neck is actually not a ConEmu "scrolling", but conhost throughput speed. Because ConEmu provides full RealConsole functions support, we can't do things "faster" than they are done by conhost. Perhaps, in future, I would implement RealConsole server internally, without need of conhost, but I can't predict any time frame.
But, I'm almost sure ConEmu may be faster than native console window, because conhost may do some optimization when its window is invisible.
I can't think of another way to describe this, but is there a way for ConEmu to 'jump' scrolling if the scrolling is too slow for the command output? (i.e. the command can generate output faster than the window can scroll it).
Terminal windows in Mac OS X and Linux desktops do this - I could
cat
a huge file which could finish in less than a second because the window doesn't scroll every line. With ConEmu, the window is scrolling every line at a slower speed than the command could potentially output it.(I hope that makes sense...?)
Versions
ConEmu build: 170402 x64 OS version: Windows 7 (6.1.7601) x64 Used shell version: git-bash, cmd