(05/18/2011 01:47 PM), Robin Lee Powell wrote: > On Wed, May 18, 2011 at 01:43:38PM -0700, Micah Cowan wrote: >> (05/18/2011 01:28 PM), Micah Cowan wrote: >>> (05/18/2011 01:19 AM), Robin Lee Powell wrote: >>>> It's vim, not less, and yes, it appears to be overwriting. >>>> >>>> The issue is that I don't have this problem in screen. >>>> >>>> OK, screenshots of screen and tmux (in alternate-screen off mode). >>>> Process is: >>>> >>>> [new window] >>>> # seq 1 100 >>>> # vim >>>> [type some crap] >>>> :q! >>>> [backscroll mode, up 10 lines, screenshot] >>> >>> To be absolutely clear, by "backscroll mode", you mean tmux's >>> copy-mode, right? It's not some scrollback that's built into the >>> terminal, is it? >> >> See, here's the thing: I can't reproduce your symptoms, even by >> catting your tmux.txt and tmux2.txt directly into my tmux session >> (with hopefully approximately the same dimensions - I'm using >> 195x73 (72 within tmux - not that it should really matter)). Every >> time, when I enter copy-mode, I can see the "150" from seq after >> exiting tmux. > > Yeah, I thought we had already established that you couldn't repro. > Catting it out has the same problems for me.
Well, we had already established that I couldn't repro via the same _steps_ as you. But now we've established that I couldn't even repro with the same exact terminal codes that were sent to tmux, which is rather different. There's plenty of ways that we could get different results from the same steps, but there aren't many ways we could get different results from the same escape sequences. Assuming that the problem is that the scrollback is being overwritten (the other possibility would be that it's not being drawn properly when you go to copy-mode, but this seems less likely), the only real explanation I can think of is that there's a crucial difference between the way our tmuxen behave, yours and mine. You mentioned not changing Putty, but I can't think of a good reason that Putty would be directly involved. Particularly since your latest script demonstrates that tmux is definitely even sending the codes to draw the appropriate bit of the scrollback. It's possible that the setting of TERM (set by Putty) could effect that in some way (what's it set to, xterm?), but beyond that... -- Micah J. Cowan http://micah.cowan.name/ ------------------------------------------------------------------------------ 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
