keyboard(6) lies

keyboard(6) lies

[Ethan Grammatikidis]

          After typing the compose key, type a lower case `x' and up
          to six hexadecimal characters (digits and `a' to `f') fol-
          lowed by a semicolon (if the sequence is less than six dig-
          its long) to type a single rune with the value represented
          by the typed number.

nope, doesn't work. i wanted to enter a literal ascii escape, so i typed
'alt, x, 1, b,' and the b appeared literally before i could enter the
semicolon. ''alt, x, 1,' had no effect. i tried a capital B, with no
change. the implication here is runes whose hex codes contain
non-decimal digits (or at least the hex digit 'b') cannot be entered.

system is 9front on r400, attempting to enter character into rio.

Re: [9front] keyboard(6) lies

[cinap_lenrek]

i dont know. works for me just fine.

alt x 1 b ; -> [like escape]

--
cinap

Re: [9front] keyboard(6) lies

[brz-systemd-dev]

It is also working for me on 9front.
It does not, however, work inside of linux drawterm.

Re: [9front] keyboard(6) lies

[cinap_lenrek]

kbdfs is not involved when you use drawterm. /dev/cons, /dev/mouse and
/dev/draw and all that stuff is done by drawterm. (its a fileserver!)

drawterm doesnt provide /dev/kbd. no playing doom for you under drawterm.

rio has a fallback so it can run without a /dev/kbd.

if you want to change compose sequence handling, you'd have to hack drawterm.

--
cinap

Re: [9front] keyboard(6) lies

[Nick Owens]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

On Tue, Feb 18, 2014 at 10:12:39AM +0100, cinap_lenrek@felloff.net wrote:
> if you want to change compose sequence handling, you'd have to hack drawterm.
> 
> --
> cinap

i started on this the other day. X11 programming sucks. there's no clear
way how to get key up/down events from X11.

mischief


[-- Attachment #2: Type: application/pgp-signature, Size: 834 bytes --]