On Tue, May 17, 2011 at 10:26:33PM -0700, Micah Cowan wrote:
> On 05/17/2011 10:21 PM, Robin Lee Powell wrote:
> >On Tue, May 17, 2011 at 09:16:16PM -0700, Micah Cowan wrote:
> >>On 05/17/2011 06:10 PM, Robin Lee Powell wrote:
> >>>
> >>>I came, over the years, to rely very much on screen's
> >>>backscroll behaviour[1], so certain aspects of tmux's behaviour
> >>>have surprised me, and I'm wondering if they can be changed.
> >>>
> >>>1.  When I quit "less", it goes away.  I'm used to the output
> >>>of less staying in the shell window/the terminal backscroll.  I
> >>>really prefer it that way.  Is that fixable?
> >>>
> >>>2.  When I launch vim or less, it ... this is hard to describe
> >>>... it covers the whole screen's worth of stuff.  So, let's
> >>>pretend my terminal is 2 lines and the backscroll is 5 lines;
> >>>current status of backscroll is:
> >>
> >>I think you may find both problems solved if you turn off the
> >>alternate-screen window option. Hope that helps.
> >
> >#1 is much better that way; yay!
> >
> >#2 is much worse; instead of overlaying the current terminal data
> >in a way that comes back when I exit or ctrl-z, it replaces it
> >permanently/unrecoverably.
> 
> "Replaces"? No, it'll scroll it off, I'd think. Which is what you
> said you wanted - all the backscroll intact. 

No, that is absolutely not what happens.

If I have:

111111111111
222222222222
333333333333
444444444444
555555555555

and I run my two-line vim, I get:

111111111111
222222222222
333333333333
XXXXXXXXXXXX
YYYYYYYYYYYY

and when I exit vim I have in backscroll I have:

111111111111
222222222222
333333333333
XXXXXXXXXXXX
YYYYYYYYYYYY

The lines that were there when I launched vim are gone.  I *just*
tested this in tmux.  I can probably arrange a screencast if you
like, or at least screenshots.

> You can't have it both ways, either in screen or in tmux: either
> you enable the alternate screen buffer, in which case the previous
> contents are not visible when you switch to it (in either less or
> vim), but are available when you quit, or you don't, and exiting
> leaves the messy remains of the application there (but the
> previous contents are usually available in the backscroll).

I very much want the messy remains and the previous contents, as I
have been used to.

-Robin

-- 
http://singinst.org/ :  Our last, best hope for a fantastic future.
Lojban (http://www.lojban.org/): The language in which "this parrot
is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
is "na nei".   My personal page: http://www.digitalkingdom.org/rlp/

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users

Reply via email to