xterm, screen and the "Home" and "End" keys
dickey at his.com
Mon Sep 8 00:50:49 UTC 2014
----- Original Message -----
| From: "Victor Sudakov" <vas at mpeks.tomsk.su>
| To: "Thomas Dickey" <dickey at his.com>
| Cc: freebsd-questions at freebsd.org
| Sent: Thursday, September 4, 2014 10:46:55 PM
| Subject: Re: xterm, screen and the "Home" and "End" keys
| Thomas Dickey wrote:
| > > > >
| > > > > alternatively:
| > > > >
| > > > > XTerm*keyboardType: vt220
| > > >
| > > > (not in "VT100")
| > >
| > > Works too, thank you.
| > > How did you know?
| > It was "an educated guess" (I maintain ncurses and xterm)
| Great! Could you try and make another educated guess? ;-) What could
| have changed in FreeBSD between 8.4 and 9.3 that caused this problem?
| I have always used vim+screen on my FreeBSD 8.4 box at work from my
| 9.3-STABLE desktop at home (over ssh, from X). The problem with the
| "Home" and "End" keys arose when I upgraded the work box to 9.3.
| Of course the upgrade involved the update of all ports, so maybe vim
| or screen are to blame and not FreeBSD per se.
termcap or xterm seem like the place to start looking (see explanation),
but I'm not aware of any recent change.
When screen starts, it takes note of the escape sequences for each of the
keys, and maps those into its own sequences. The sequences you expect for
screen's own look okay.
Since you're _getting_ those sequences, it sounds as if xterm's been changed,
e.g., with a port option to send the VT220-keyboard. That's a runtime default
that can be overridden with the control/left/mouse menu. I'd compare the
local / remote xterms' setting on that menu, to see if the misbehaving one
has the "VT220 Keyboard" menu entry selected.
Thomas E. Dickey <dickey at invisible-island.net>
More information about the freebsd-questions