rvaiya
[X11] unicode char mapping does not work
As per this comment, my understanding is following should work:
[ids]
*
[main]
o = ö
$ sudo service keyd restart
$ setxkbmap -option compose:menu # for good measure
Yet when o is typed:
$ 03a
What am I doing wrong?
$ keyd --version
keyd v2.4.3 ()
Also this bit under Unicode Support in manual is a bit confusing:
In order for this to work, the sequences defined in the compose file shipped with keyd (/usr/share/keyd/keyd.compose) must be accessible
Symlinked /usr/share/keyd/keyd.compose to both my regular user & root's homedir at ~/.XCompose, but that didn't change anything.
Note the shiftedDia version proposed here works perfectly. Are there any considerations whether the macro(compose) should be preferred or avoided over the direct UTF mapping? Is any method generally better, e.g. in terms of cross-x11/wayland functionality?
The 'direct' UTF mapping just transparently creates a macro that does the same thing (you can see what keys keyd is actually outputting using keyd monitor). Symbols are a compositor level thing, and the current approach has some limitations (see #470). Does this happen in every application? What desktop environment are you using?
Not using DE nor a compositor - running a simple i3 session.
keyd monitor doesn't show any output on typing letters.
It happens with every program as far as I can tell - browsers, urxvt, xterm, discord, slack, signal, spotify, geany, intellij idea, vnote...
- running a simple i3 session.
This should work, as most of the XCompose issues are caused by wayland and/or GTK4.
keyd monitor doesn't show any output on typing letters.
Try sudo keyd monitor, if you are seeing any output it should be captured by the monitor command.
It happens with every program as far as I can tell
Have you tried restarting your X session since symlinking the file? Can you double check that the compose contents are actually accessible? (wc -l ~/.XCompose should yield a number in the thousands)