removing kH and *6 from xterm

[Rong-en Fan]

On Jan 5, 2008 2:04 AM, Ulrich Spoerlein <uspoerlein at gmail.com> wrote:
> Hi Rong-en,
>
> On Thu, 03.01.2008 at 09:47:34 +0800, Rong-en Fan wrote:
> > Hi folks,
> >
> > Recently, I'm looking into 100150 which reports END key does not working in
> > mutt. With some help from ncurses author, I think this problem is caused by
> > our termcap. To be specific, our termcap defines kH, @7 (the END key), and *6
> > to \EOF. ncurses has the limitation that it will only return the first matched
> > key back. So, in ncurses based program, it receives kH instead of @7 when you
> > hit END.
>
> Thanks for taking up the ball! It is not only the END key, though. The
> KP_Enter is missing, too.
>
> Is there some documentation on what kH, @7, etc. all means? I see that
> Home (^[OH) and End (^[OF) are there in /etc/termcap but only Return
> (^M) and not KP_Enter (^[OM). What would be the symbol required to map
> ^[OM to?
>
> I see that vt100 has @8=\EOM, is this what I'm looking for and do we
> want it in the xterm definition?
>
> > I just checked NetBSD's termcap, they only defines @7 to \EOF in xterm entry.
> > Also, on a Linux box, infocmp shows that only @7 is defined but not *6 and kH.
> > So, I'm wondering whether we should remove those two keys (kH and @7)?
>
> They also define @8=\EOM right next to @7.
>
> I wonder, though, how do I activate the change? I changed /etc/termcap,
> opened a new xterm but mutt's behaviour hasn't changed ...

I'm proposing the following change:

http://people.freebsd.org/~rafan/termcap-xterm.diff

which removes kH, *6 from xterm and adds @8 (enter key) to it.

Any objections?

Thanks,
Rong-En Fan

>
> Cheers,
> Ulrich Spoerlein
> --
> It is better to remain silent and be thought a fool,
> than to speak, and remove all doubt.
>