Date: Thu, 6 Oct 2011 19:37:25 -0400 From: Thomas Dickey <dickey@radix.net> To: Gary Kline <kline@thought.org> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: OT: how to tell when i've hit a Fn key? Message-ID: <20111006233725.GA18837@saltmine.radix.net> In-Reply-To: <20111006224114.GA15978@thought.org> References: <20111006224114.GA15978@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 06, 2011 at 03:41:17PM -0700, Gary Kline wrote: >=20 > I've got a 103-key keyboard. most of them produce the right WAV > file. i was having some trouble with the arrow key, but think i've > found a resolution. next are the Function key, F1 to F12.=20 >=20 > anybody on-list familiar with curses and can help me with this? > right now, most of the function keys output 4 clicks [!]. =20 I generally use tack for verifying the function-keys against the terminal description. (I don't recall seeing a port for tack, but it can probably be built starting with ncurses-devel, though I haven't tried that, since I build development versions of ncurses outside the ports). For _seeing_ the codes, it helps to type ^V (lnext) right before pressing a given key, making the escape character visible. --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFOjjuztIqByHxlDocRAnGgAKCwKZLERdmbdhYCY3tQx9Ovs3XbrgCfQao2 xZ6aH0Mfryz362u6yhsWzFk= =thCf -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111006233725.GA18837>