Comment 111 for bug 1245473

Oleg: I tried xneur and it obviously solves some problem for someone, but not this problem for me. For once it doesn't play nice with X.org (if I understand correctly it takes over keyboard input completely and handles it on its own), for second it only supports a small subset of languages supported in X.org and for third its way too complicated.

Adam Purkrt discussion about the changes required, and nonZero's idea for implementation look like a very good thing to implement. I understand from Adam Purkrt's comments that this suggestion conflicts with the specification of the XKB protocol - Is that correct? and if so - can it be implemented regardless in X.org or does the X.org development process calls for the specification to first be changed?

Also regarding the recency list idea described in Adam Purkrt's last comment - I think that the idea in itself is good but the implementation, especially the part where the system should switch from responding to RELEASE event to use PRESS events instead, is way complicated and we should start by getting the "switch on release" working first so that layout switching can actually be done without interfering with shortcuts, and do optimization later.

I'm not an X.org developer, but I'm a programmer by trade and if this can be fixed in X.org (see my previous questions), I would really like to try to put in a fix according to Adam's and nonZero's suggestions. I just wouldn't like to invest a lot of work in this only to find its all for naught, so I'd appreciate some feedback from the developers first (Daniel?) if this is even feasible to do in the X.org code base (i.e. without getting into a large protocol specification process).