[e-users] e16 Special-key keybindings not working cont'd

[Dennis N. <de...@de...>]

I posted a couple of months ago about this issue (end of august), and
still haven't managed to resolve it :P. So, to recap:

* No keybindings of "special keys" work on my acer laptop keyboard
(Option "XkbModel" "acer_ferrari4k") like XF86Mail, EuroSign, when
e16 FIRST starts up--but they do with 'eesh restart'. This suggests that
the problem is not with my configuration, but with the way e16 "grabs"
control of the keyboard; perhaps a timing issue. Keybindings of
"normal" keys always work. It should be noted that the special keys are
recognized (xev)--just not bound.

* An interesting anomaly is the normal 'dollar' symbol. My laptop has
another separate key just for it, in addition to the normal one above
the '4' key. But if I make a keybinding to 'dollar', it will trigger
when I press '4' (not Shift-4). This problem of having the
"shift-level" symbol being interpreted as the "first level" only exists
with this duplicated dollar symbol, and not with others like 'at' or
'numbersign'. If I remove 'dollar' from my bindings.cfg, the '4' key is
once again interpreted as '4', and not the key-bound dollar, which
suggests that the problem has something to do with e16's key binding
mechanism.

* Most interesting of all, starting e16 with null theme (removing the
theme folders; eesh theme says Name: (null)) makes the "special key"
bindings work! This suggests that the bug has something to do with
e16--even though it was only when I upgraded X (or one of X's keyboard
modules) that the problem started. How can the keybinding process
possibly differ if no theme is present versus if a theme is loaded??

In other words, there's something about having no theme, or restarting
e16, that makes things work--or something about initially loading a
theme that breaks key bindings. I don't know enough about X or e16
keybinding internals to put all these pieces of the puzzle together.
Hopefully someone else might?