Date: Sat, 5 Jan 2008 06:50:18 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Rong-en Fan <grafan@gmail.com>, freebsd-arch@freebsd.org Subject: Re: removing kH and *6 from xterm Message-ID: <20080104195018.GN947@server.vk2pj.dyndns.org> 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
--IbVRjBtIbJdbeK1C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 04, 2008 at 07:04:29PM +0100, Ulrich Spoerlein wrote: >Is there some documentation on what kH, @7, etc. all means? See terminfo(5). Note that this only documents what capabilities are available to describe terminals. It doesn't mean that those capabilities are actually used by a specific application. >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? There's only provision for a single 'key_enter' (enter/send key) code - "@8" in termcap. >I wonder, though, how do I activate the change? I changed /etc/termcap, >opened a new xterm but mutt's behaviour hasn't changed ... Check if you have $TERMCAP as the terminal's expanded termcap entry. TERMCAP=3D'...' mutt works for me. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --IbVRjBtIbJdbeK1C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHfo36/opHv/APuIcRAi+jAJ9uA7ksAOak2TFX0UDggKuMubnS+QCfQnWJ x9ezcVgwZ9basJEHtoma/fk= =GG08 -----END PGP SIGNATURE----- --IbVRjBtIbJdbeK1C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080104195018.GN947>