Logs on 2022-06-10 (liberachat/#kmonad)
| 08:45:21 | <noze> | okay, I did that, but it wasn't so trivial; I had to set my wayland layout to US first |
| 08:47:08 | <noze> | what's the right way to get richer unicode input? |
| 08:55:24 | <Solid> | unicode entry on GNU/Linux is done via compose key sequences |
| 08:55:34 | <Solid> | I don't know if wayland supports those |
| 08:55:44 | <Solid> | but on X11 you just instert the unicode character verbatim and it should just work |
| 08:56:54 | <noze> | xcompose sort of works under wayland, but I can't seem to figure out how to reload it without restarting my session. oh well... |
| 08:58:43 | <noze> | do you know if there's a way to enter a character by typing out its code? E.g. if I want to type a single 'A' (silly example), I'd type 0x41, or 65 |
| 09:00:10 | × | pils[m] quits (~pilscatca@2001:470:69fc:105::2:b9c) (Quit: You have been kicked for being idle) |
| 09:00:23 | <noze> | as in, is there a `read_unicode_sequence` such that I can bind <Multi_key><U><U> to read_unicode_sequence, and then type out the sequence? |
| 09:00:42 | → | pils[m] joins (~pilscatca@2001:470:69fc:105::2:b9c) |
| 09:03:43 | ← | pils[m] parts (~pilscatca@2001:470:69fc:105::2:b9c) () |
| 09:07:10 | <noze> | Is it possible to emit keys that are not listed in Keycode.hs? |
| 09:10:34 | <noze> | a lot of keys are defined in /usr/include/X11/keysymdef.h |
| 09:10:34 | <noze> | can kmonad emit them? |
| 09:34:34 | <Solid> | the answer to the first question is no; kmonad is relatively low-level and so a priori only knows about keycodes that the linux kernel itself specifies; definitely no unicode, as how exactly input works there is the job of the environment |
| 09:35:17 | <Solid> | There is KMonad.Keyboard.ComposeSeq for all kinds of compose key sequences that are accepted by default |
| 09:35:27 | <Solid> | i.e., the unicode character itself should work |
| 09:35:54 | <Solid> | for anyting else you would have to specify a macro manually (like #(menu " s) or something) |
| 09:37:29 | <noze> | thank you Solid for all the explanations :) |
| 09:39:21 | <noze> | okay so I guess I'll just have to bite the bullet and work with an additional level of indirection; it would have been nice to just specify the unicode code point in kmonad, but unless there's something like read_unicode_sequence I don't see how that could be made to work |
| 09:40:11 | <Solid> | yeah it's not completely out of the question that this will ever be supported, but it's definitely in at least the medium future |
| 09:41:02 | <Solid> | you'd have to recognise the environment in which kmonad was started somehow, which is hard in itself, but then people who start it as a service surely also want unicode entry, so it's more like the "best current environment" |
| 09:41:08 | <Solid> | which tbh sounds like a bit of a nightmare |
| 09:41:25 | <Solid> | and I don't even know if there is a reliable way to input unicode in e.g a TTY |
| 09:41:36 | <Solid> | (without going via keymaps and all that) |
| 16:26:27 | <noze> | okay, so xcompose only seems to support input sequences up to length 8, but with that I was able to code any 6 hex digit unicode char "FOO" with code '0x9ABCDE' as <Multi_key> <u> <x> <9> <a> <b> <c> <d> <e> : "FOO" |
All times are in UTC on 2022-06-10.