On Sat, Feb 06, 2010 at 11:17:03PM +0100, clemens fischer wrote:
> Micah Cowan wrote:
> 
> > clemens fischer wrote:
> >> Micah Cowan wrote:
> >> 
> >>> I think he's referring to the alternate buffer.
> >>>
> >>> clemens, one way of working around that would be to simply suspend
> >>> less or vim (or whatever) with C-z, enter copy-mode and grab what
> >>> you want, then exit copy-mode and resume your app.
> >> 
> >> Oh, I'm doing that all the time, but no dice.  Suspend vim and poof,
> >> I get to see whatever was on screen before that, but nothing from the
> >> screen session.
> > 
> > Then I'm not understanding what you're asking for.
> 
> I'm sorry, my description was wrong.  It should have read:
> 
>   Oh, I'm doing that all the time, but no dice.  Suspend vim and poof,
>   I get to see whatever was on screen before that, but nothing from the
>   _vim_ session.
> 
> What I'd like to see after exiting from or suspending vim is this:
> 
>   --- (part of) vim output:
>   ...
>          /*
>           * Enter alternative screen mode. A copy of the visible
>           * screen is saved and the history is not updated
>           */
>   ...
>   
> /mnt/backup/no-backup/src/bulk/console/tmux/repo-cvs/tmux-build-spott/input.c,C
>   --- right next comes some bash interaction:
>   [1]+  3720 Stopped                 vim -p input.c
>   /src/bulk/console/tmux/repo-cvs/tmux-build-spott
>   $ hi 5
>    1027  100206-22:44 g saved_grid *.c
>    1028  100206-22:45 v /root/.tmux*
>    1029  100206-22:46 tmux set-option -g status-interval 12
>    1030  100206-22:47 newsq
>    1031  100206-22:54 hi 5
> 
> Instead there's nothing from the vim screen and I just see bash
> interaction stuff.  This happens with all curses programs, and it might
> have to do with saving the grid in input_handle_sequence_sm()@input.c on
> every curses initialisation.  If this is the case, there should be an
> option to switch it off.  The way I see it this option should still save
> the original grid coordinates to be able to restore it properly in
> input_handle_sequence_rm()@input.c.
> 
> The problem I see looking at lines 1189pp @ input.c is the GRID_HISTORY
> flag, which is supposed to be off after handling the sm sequence.  I'm
> not sure if it should stay on if a new option disables the saved_grid.
> 

You should be able to disable this behaviour my modifying the screen terminfo
entry to remove smcup and rmcup. You can use infocmp to put it in a file then
tic to compile it to ~/.terminfo.

> 
> clemens
> 
> 
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users

Reply via email to