Re: Window resizing and F10 not working

2005-08-12 Thread Trebor Sreyb
--- Michael Schroeder <[EMAIL PROTECTED]> wrote: > Okay, start screen and press ^V F10 (^V is Control > V). Then do 'infocmp screen' and check if the kf10 > entry matches this string (\E is ^[). (The string > should be "^[[21~", btw.) Thanks, it appears F10 is not properly mapped (^[[10~ instead

Re: Window resizing and F10 not working

2005-08-12 Thread Michael Schroeder
On Fri, Aug 12, 2005 at 09:00:02AM -0700, Trebor Sreyb wrote: > > > (after re-entering insert mode after F10 took me out > of insert mode) > > The *only* difference is that screen was used in the > later example. Hence, screen is handling F10 a bit > differently. Okay, start screen and press ^V

Re: Window resizing and F10 not working

2005-08-12 Thread Trebor Sreyb
--- Michael Schroeder <[EMAIL PROTECTED]> wrote: > I don't see how this can help. It's not the 'screen' > termcap/info entry that are missing the resize codes, > but your terminal emulator's entries. Try 'echo > $TERM' before you start screen. > > (And your terminfo entry is wrong, it should > p

Re: Window resizing and F10 not working

2005-08-12 Thread Michael Schroeder
On Thu, Aug 11, 2005 at 11:10:25AM -0700, Trebor Sreyb wrote: > OK, my head is spinning like a top. There are two > problems I'm having with screen: > > 1. Cannot resize the window ("Your termcap does not > specify how to change the terminal's width to 132") > > 2. Function key F10 is not properl