Re: Window resizing and F10 not working

[Trebor Sreyb]

--- Michael Schroeder
<address@hidden> 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
> probably read WS=\E[8;%p1%d;%p2%dt'. If the codes
> are always the same we wouldn't need two different
> commands...)

My TERM _prior_ to starting screen is:

% echo $TERM 
xterm

After I start screen, my TERM is:

% echo $TERM 
screen


I think I was using Ctrl-A,W incorrectly. The manpage
for screen says Ctrl-A,W will toggle between 80 and
132 columns, which is not exactly what I want.

Instead, I found that the screen command 'fit' will do
exactly what I'm asking. So this particular issue is
now resolved.




Now on to my other problem : the F10 function key is
somehow not treated like the other function keys.

If I start vim (version 6.2), go into insert mode,
then press the F2 through F12 function keys one by
one, I get the string '<Fn>' entered into the document
for each function key, like this:

<F2><F3><F4><F5><F6><F7><F8><F9><F10><F11><F12>


However, if I start screen, then run vim from inside
the screen session, and repeat the same keystrokes,
all the keys EXCEPT F10 get treated just as before. 

With F10, something different is sent - I'm not
exactly what is sent, although an escape character
must be part of it since it breaks me out of insert
mode. For example, I get this via vim in screen:

<F2><F3><F4><F5><F6><F7><F8><F9><F11><F12>

(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.

Thanks,
-bob
 Andover, MA
 USA




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com