Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Jan 2008 20:41:09 +0100
From:      Erik Trulsson <ertr1013@student.uu.se>
To:        Rong-en Fan <grafan@gmail.com>, freebsd-arch@freebsd.org
Subject:   Re: removing kH and *6 from xterm
Message-ID:  <20080104194108.GA47714@owl.midgard.homeip.net>
In-Reply-To: <20080104180429.GA1496@roadrunner.spoerlein.net>
References:  <6eb82e0801021747w73a04d5ckc0a7ef623a806302@mail.gmail.com> <20080104180429.GA1496@roadrunner.spoerlein.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 04, 2008 at 07:04:29PM +0100, Ulrich Spoerlein 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?


Read the termcap(5) and terminfo(5) manpages.  They should include all
information you might need about terminal capabilities.


> 
> > 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 believe most programs look in /usr/share/misc/termcap.db (built from
/usr/share/misc/termcap with cap_mkdb(1))


-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080104194108.GA47714>