* Re: [9fans] KF|12, etc
@ 2014-03-22 22:06 Erik Quanstrom
0 siblings, 0 replies; 6+ messages in thread
From: Erik Quanstrom @ 2014-03-22 22:06 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
example: apple USB full sized kbd. f13 doesn't work. it has up to f18 USB does define these keys.
cinap_lenrek@felloff.net wrote:
>this is hexadecimal. KF|1 .. KF|0xC -> F1 .. F12.
>not sure tho about F13-F24. never seen a keyboard
>like that.
>
>--
>cinap
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] KF|12, etc
2014-03-23 3:09 ` Charles Forsyth
@ 2014-03-23 5:59 ` erik quanstrom
0 siblings, 0 replies; 6+ messages in thread
From: erik quanstrom @ 2014-03-23 5:59 UTC (permalink / raw)
To: 9fans
> I suspect it was meant to describe a new internal sequence of values in the
> 0x1x range, which wasn't thought to be used.
i ment the question in terms of how to we fix it in a coordinated way.
it's not just the f keys, but there are other keys that are common these
days that seem useful.
- erik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] KF|12, etc
2014-03-22 20:03 erik quanstrom
2014-03-22 21:58 ` cinap_lenrek
@ 2014-03-23 3:09 ` Charles Forsyth
2014-03-23 5:59 ` erik quanstrom
1 sibling, 1 reply; 6+ messages in thread
From: Charles Forsyth @ 2014-03-23 3:09 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
On 22 March 2014 20:03, erik quanstrom <quanstro@quanstro.net> wrote:
>
> Kleft= KF|0x11,
> Kright= KF|0x12,
I suspect it was meant to describe a new internal sequence of values in the
0x1x range, which wasn't thought to be used.
[-- Attachment #2: Type: text/html, Size: 564 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] KF|12, etc
2014-03-22 21:58 ` cinap_lenrek
@ 2014-03-23 1:01 ` erik quanstrom
0 siblings, 0 replies; 6+ messages in thread
From: erik quanstrom @ 2014-03-23 1:01 UTC (permalink / raw)
To: 9fans
also, i mix up kbd.c with /sys/include/keyboard.h. sorry.
why keyboard.h uses hex is beyond me. nobody ever says
press the f0xa key.
kbd.c has the more sensible
Home= KF|13, /* failure of vision; collides with f keys */
Up= KF|14,
Pgup= KF|15,
but it's also true that f11,f12 did not work before with usb.
that was a table issue. (patch submitted.)
- erik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] KF|12, etc
2014-03-22 20:03 erik quanstrom
@ 2014-03-22 21:58 ` cinap_lenrek
2014-03-23 1:01 ` erik quanstrom
2014-03-23 3:09 ` Charles Forsyth
1 sibling, 1 reply; 6+ messages in thread
From: cinap_lenrek @ 2014-03-22 21:58 UTC (permalink / raw)
To: 9fans
this is hexadecimal. KF|1 .. KF|0xC -> F1 .. F12.
not sure tho about F13-F24. never seen a keyboard
like that.
--
cinap
^ permalink raw reply [flat|nested] 6+ messages in thread
* [9fans] KF|12, etc
@ 2014-03-22 20:03 erik quanstrom
2014-03-22 21:58 ` cinap_lenrek
2014-03-23 3:09 ` Charles Forsyth
0 siblings, 2 replies; 6+ messages in thread
From: erik quanstrom @ 2014-03-22 20:03 UTC (permalink / raw)
To: 9fans
as i mentioned before, these definitions are puzzling:
Kleft= KF|0x11,
Kright= KF|0x12,
these overlap with f11 and f12. since f11-f24 are all defined,
wouldn't it make more sense to move Kleft, etc. out of the way?
- erik
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-03-23 5:59 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-22 22:06 [9fans] KF|12, etc Erik Quanstrom
-- strict thread matches above, loose matches on Subject: below --
2014-03-22 20:03 erik quanstrom
2014-03-22 21:58 ` cinap_lenrek
2014-03-23 1:01 ` erik quanstrom
2014-03-23 3:09 ` Charles Forsyth
2014-03-23 5:59 ` erik quanstrom
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).