Re: terminal-overrides: proper terminfo entries?

2010-02-06 Thread Micah Cowan
Nicholas Marriott wrote: - Any time I view a manual page, use the less pager or the vim editor, I get a fresh screen page. This disturbs me somewhat, because I'm used to go up in copy-mode, select some text and paste it where it's needed. I don't understand what you mean by this. I

Re: terminal-overrides: proper terminfo entries?

2010-02-06 Thread Micah Cowan
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

Re: terminal-overrides: proper terminfo entries?

2010-02-06 Thread clemens fischer
Micah Cowan wrote: I think he's referring to the alternate buffer. I'm sorry: where is this alternate buffer implemented? Does it have to do with input.c: * Enter alternative screen mode. and the *saved_grid pointer? Maybe I should try to add an option for switching it off, per window or

Re: terminal-overrides: proper terminfo entries?

2010-02-06 Thread Micah Cowan
clemens fischer wrote: 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. My guess would be that this flag controls whether or not

Re: terminal-overrides: proper terminfo entries?

2010-02-06 Thread clemens fischer
Nicholas Marriott wrote: On Sat, Feb 06, 2010 at 11:17:03PM +0100, clemens fischer wrote: 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