I know it's been ages, but do you have an emacs-level fix for this?
If you do, I'd be happy to include it in emacs20 as long as it doesn't
break any expected upstream behavior...
Kirk Hilliard <[EMAIL PROTECTED]> writes:
> xterm now has the following resource set:
>
> *VT100.Translations: \
> #override ~Shift ~Ctrl ~Meta <Key>BackSpace: string("\177")\n \
> ~Shift ~Ctrl ~Meta <Key>Delete: string("\033[3~")\n \
> ~Shift ~Ctrl ~Meta <Key>Home: string("\033[1~")\n \
> ~Shift ~Ctrl ~Meta <Key>End: string("\033[4~")
>
> (I'm not sure when this changed from what it used to be: "\033OH: for
> Home and "\033OF" for End.)
>
> However all four flavors/versions of emacs contain lisp/term/xterm.el
> files which say:
>
> (define-key function-key-map "\e[4~" [select])
>
> Thus the END key does not work in "emacs -nw" in an xterm.
>
> (The xemacs files also define "\e[1~" as [find], breaking the HOME key.)
>
> Kirk Hilliard
>
>
> Offending Files:
>
> /usr/share/emacs/19.34/lisp/term/xterm.elc
> /usr/share/emacs/19.34/lisp/term/xterm.el
> /usr/share/emacs/20.5/lisp/term/xterm.elc
> /usr/share/emacs/20.5/lisp/term/xterm.el
> /usr/lib/xemacs-20.4/lisp/term/xterm.elc
> /usr/lib/xemacs-20.4/lisp/term/xterm.el.gz
> /usr/lib/xemacs-21.1.8/lisp/term/xterm.elc
> /usr/lib/xemacs-21.1.8/lisp/term/xterm.el.gz
>
> Offending Packages:
>
> emacs19
> emacs20
> emacs20-el
> xemacs20-support
> xemacs20-supportel
> xemacs21-support
> xemacs21-supportel
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
