screen scrollback
Brian Kelsay
bkelsay at comcast.net
Tue Nov 30 20:00:39 CST 2004
I used a lot more words to say it, but the info at the bottom was
present in my quotation of the Fine Manual. I later went on to describe
the salient points of interaction between terminal window and program,
i.e. screen. I suppose I could learn to read minds, you could give me
my own login and I could do stuff for you, but what would be the point
in that?
I try to give clear answers, quote where appropriate, give an URL to my
source and flesh out unspoken details. All this so that I and others
may learn more. Where's that link to the Jargon File on asking good
questions?
Jonathan Hutchins wrote:
> On Tuesday 30 November 2004 02:49 pm, Bill Cavalieri wrote:
>
>
>>>The problem is that when running screen in a terminal window, screen
>>>tends to intercept the scrollback buffer. This means that whatever
>>>you've configured for the terminal program is often irrelevant, as is the
>>>terminal program's normal scrollback function.
>
> (Meaning, aparantly, "How is normal scrollback functionality to be maintained
> when using multiple screen sessions?")
>
> That's easy: Just like putty does it.
>
> Yes, each session in screen needs it's own buffer. No, I'm not sure how putty
> achieves this.
>
> I'm also not able to check to make sure putty works with multiple screen
> sessions, if at all. I do know that my default xterm will not scroll back
> with a _single_ screen session - the buffer indicator goes to 100% when I
> launch screen.
>
> I have read the manuals, which is why I find it frustrating when people on the
> list just quote man pages at me regarding this. They don't actually address
> the problem.
>
> Thank YOU very much though, you found the answer:
>
> Place
>
> termcapinfo xterm ti@:te@
>
> in your .screenrc file.
>
> (better yet in /etc/screenrc)
>
More information about the Kclug
mailing list