Hallo, Thomas Dickey schrieb am Wed 12. Nov, 17:12 (-0500): > On Tue, 11 Nov 2008, Jörg Sommer wrote: > >> Package: ncurses-base >> Version: 5.7-1 >> Severity: normal >> >> I'm in an XTerm (package version 237-1): >> >> % echo $TERM >> xterm >> % infocmp -L G -Eo 'key_(home|end|up|down)=[^,]*' >> key_down=\EOB >> key_end=\EOF >> key_home=\EOH >> key_up=\EOA >> >> but XTerm sends these sequences: >> >> % read >> ^[[B^[[4~^[[1~^[[A >> >> They match the sequences defined for the linux console and comply with >> the recommend “9.8. Keyboard configuration” of the Debian Policy: >> >> % infocmp -L linux G -Eo 'key_(home|end|up|down)=[^,]*' >> key_down=\E[B >> key_end=\E[4~ >> key_home=\E[1~ >> key_up=\E[A >> >> So you should change the terminfo for xterm otherwise some programs might >> not work, because they expect wrong key sequences read from the terminfo. > > Actually the only impact I've seen is on bash users, who typically > hardcode their function key definitions.
I have a problem with jed that configures the keys according the
information in terminfo and fails with the different keys send by XTerm.
Why the terminfo says XTerm sends \EOA for up, but XTerm send \e[A?
Have a nice day, Jörg.
--
Als deutscher Tourist im Ausland steht man vor der Frage, ob man sich
anständig benehmen muss oder ob schon deutsche Touristen dagewesen sind.
(Kurt Tucholsky)
signature.asc
Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP
