Am 05.11.2016 20:03, schrieb Mihail Konev:
> The overlay_keys array could be avoided.
>
> Testcase:
>
> // In the exact order:
> // - press Insert
> // - press Tilde
> // - release Insert
> // - wait
> // - release Tilde
> //
> // Keyboard input would be locked.
>
> xkb_keymap {
>
On Sun, Nov 06, 2016 at 12:37:44AM +0500, Mihail Konev wrote:
> The only reason not to use arrow-keysyms-on-levels is that
> MonoDevelop, Java apps, VTE do not recognize them as "arrows",
> i.e. you cannot shift-select, or shift-scroll.
>
> A possible solution to avoid abovementioned indirection
On Sat, Nov 05, 2016 at 03:43:49AM +0500, Mihail Konev wrote:
> On Sat, Nov 05, 2016 at 03:26:54AM +0500, Mihail Konev wrote:
> > E.g. you cannot have caps+y be 'yen' and 'YEN' easily.
> (Assuming that Unicode 'yen' does not capitalize to 'YEN').
> E.g. caps+y -> ':' ; caps+Y -> '@' .
Correct
On Sun, Nov 06, 2016 at 12:03:47AM +0500, Mihail Konev wrote:
> +if (overlay_enabled)
> +overlay_keys[which_overlay][(unsigned char)key] =
> behavior.data;
> +else
> +behavior_data = overlay_keys[which_overlay][(unsigned
> char)key];
> +
The overlay_keys array could be avoided.
Testcase:
// In the exact order:
// - press Insert
// - press Tilde
// - release Insert
// - wait
// - release Tilde
//
// Keyboard input would be locked.
xkb_keymap {
xkb_keycodes { include "evdev" };
xkb_types{ include "complete" };
The overlay_keys array could be avoided.
Testcase:
// In the exact order:
// - press Insert
// - press Tilde
// - release Insert
// - wait
// - release Tilde
//
// Keyboard input would be locked.
xkb_keymap {
xkb_keycodes { include "evdev" };
xkb_types{ include "complete" };
> Question is, was it there for 22 years cause it's unfixable or because
> nobody uses overlay? :)
I guess Mihail is right, overlays are certainly little used. I do use
overlays myself, but only as as lock, where the bug is not likely to
occur.
You might want to look at Redirect actions,
