From: Stuart Longland <stuartl@vrt.com.au>
To: yocto@yoctoproject.org
Subject: Re: matchbox-terminal and function keys
Date: Fri, 28 Mar 2014 09:01:15 +1000 [thread overview]
Message-ID: <5334ADBB.6020008@vrt.com.au> (raw)
In-Reply-To: <5334829A.80001@vrt.com.au>
On 28/03/14 05:57, Stuart Longland wrote:
> Hi Ross,
> On 27/03/14 22:27, Burton, Ross wrote:
>> Can you paste the output of cat to confirm the values you're seeing?
>> The xterm guide says VT100 for F1-F4 (as VT100 doesn't define F5
>> onwards) and VT220 for F5-F10 and that's what I'm seeing when I
>> attempt this (F10 specifically being ^[[21~).
>
> Well, evidently the ncurses devs didn't get that memo as F1-F5 aren't
> recognised when TERM=xterm. I understood xterm was a superset of vt220.
>
> I'll do a `cat` to a file and post the contents when I get in. I'm just
> confused as to why ncurses applications don't seem to recognise F1-F5.
Okay, I've done a `cat` of the respective keys:
> root@xg100:~# hexdump -C /tmp/fn
> 00000000 1b 4f 50 1b 4f 51 1b 4f 52 1b 4f 53 1b 5b 31 35 |.OP.OQ.OR.OS.[15|
> 00000010 7e 1b 5b 31 37 7e 1b 5b 31 38 7e 1b 5b 31 39 7e |~.[17~.[18~.[19~|
> 00000020 1b 5b 32 30 7e 1b 5b 32 31 7e 0a |.[20~.[21~.|
So it indeed is sending those key commands. I've discovered that if I
set TERM=xterm-xfree86, things work so evidently the ncurses here has
something funny with its 'xterm' terminfo entry.
Is there a way to override the terminal type set by matchbox-terminal?
Regards,
--
Stuart Longland
Systems Engineer
_ ___
\ /|_) | T: +61 7 3535 9619
\/ | \ | 38b Douglas Street F: +61 7 3535 9699
SYSTEMS Milton QLD 4064 http://www.vrt.com.au
prev parent reply other threads:[~2014-03-27 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 5:50 matchbox-terminal and function keys Stuart Longland
2014-03-27 12:27 ` Burton, Ross
2014-03-27 19:57 ` Stuart Longland
2014-03-27 23:01 ` Stuart Longland [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5334ADBB.6020008@vrt.com.au \
--to=stuartl@vrt.com.au \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.