Bug 185582 - Secondary Scroll Buffer for Screen in Konsole
Summary: Secondary Scroll Buffer for Screen in Konsole
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
: 123643 321949 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-26 10:08 UTC by Rasmus Steinke
Modified: 2018-02-28 18:53 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Comparison of konsole and urxvt (72.35 KB, image/png)
2009-03-17 00:51 UTC, Rasmus Steinke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rasmus Steinke 2009-02-26 10:08:23 UTC
Version:            (using KDE 4.2.0)
Installed from:    Unlisted Binary Package

urxvt has this really nice feature that creates a 2nd buffer for screen windows that can easily be scrolled up/down with the regular pgup/pgdown keys.

Having this in konsole would really be nice.
Comment 1 Robert Knight 2009-02-26 13:57:17 UTC
Konsole does support a secondary scroll buffer.  You'll see it used when you run Vim or Less.  I'll have to look into why Screen isn't using it.
Comment 2 Matthew Woehlke 2009-03-16 21:22:54 UTC
Rasmus: what is $TERM for uxvt, and for Konsole?
Comment 3 Rasmus Steinke 2009-03-16 22:50:18 UTC
carnager@freebox ~ % echo $TERM
rxvt-unicode

carnager@freebox ~ % echo $TERM
xterm
Comment 4 Rasmus Steinke 2009-03-16 22:56:47 UTC
When i set it to rxvt-unicode it *somewhat* works, but it behaves strange... e.g. irssi will lose all the timestamps when scrolling up...
Comment 5 Matthew Woehlke 2009-03-16 23:49:30 UTC
Thanks; that implies there may be nothing "wrong" with Konsole per-se, but that your programs aren't making use of Konsole's features correctly due to a sub-optimal TERM setting.

Does uxvt still "work" if you change TERM to xterm? If yes, that implies it may be more directly Konsole's fault. If not it may just be that you need a "better" TERM when using Konsole.

(In either case, Robert will likely be of more help at this point; I'm just filling in the "likely suspects" stuff, I don't know that much about the technical details of Konsole or terminal capabilities.)
Comment 6 Rasmus Steinke 2009-03-17 00:43:17 UTC
urxvt still works if TERM is set to xterm, but it also behaves a little different in that case. It does not mess the screen details up, like konsole with "rxvt-unicode" tho.
Comment 7 Rasmus Steinke 2009-03-17 00:46:56 UTC
To be precise: Somehow urxvt manages it to keep the hardstatusline at the bottom of the terminal. This only works if TERM is set to rxvt-unicode.
If i set it to xterm, i can still scrollback, but the hardstatusline is scrolled with the rest.

In terminal i get either the (unwanted) behavior of the latter (plus some obvious glitches) or nothing at all.
Comment 8 Rasmus Steinke 2009-03-17 00:51:46 UTC
Created attachment 32171 [details]
Comparison of konsole and urxvt
Comment 9 Rasmus Steinke 2009-03-17 00:53:03 UTC
And no: those are not just wrong configured colors, the text is really missing :) The text instantly appears if i set TERM back to xterm.
Comment 10 Robert Knight 2009-03-17 11:35:46 UTC
Konsole is for the most part supposed to be 'xterm compatible' and should advertise pretty much the same capabilities possibly with a few extras.  I use the vttest program written by the X term developer for checking compatibility.
Comment 11 Rasmus Steinke 2009-03-17 21:24:29 UTC
Well i guess screen itself does something wrong then. Which is sad, because without scrollback screen is only half as fun. (They seem to know about it tho, otherwise screen wouldnt have its own buffer i guess - but its not as nice to use as a *real* scrollback)
Comment 12 Ahmad Samir 2018-02-28 18:51:08 UTC
*** Bug 321949 has been marked as a duplicate of this bug. ***
Comment 13 Ahmad Samir 2018-02-28 18:51:40 UTC
*** Bug 123643 has been marked as a duplicate of this bug. ***
Comment 14 Ahmad Samir 2018-02-28 18:53:43 UTC
See bug 123643 comment0 for more info.