Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compose sequence terminates after pressing ISO_LEVEL5_SHIFT #413

Closed
rexVictor opened this issue Dec 5, 2023 · 1 comment · Fixed by #415
Closed

Compose sequence terminates after pressing ISO_LEVEL5_SHIFT #413

rexVictor opened this issue Dec 5, 2023 · 1 comment · Fixed by #415
Labels
bug Indicates an unexpected problem or unintended behavior keysyms

Comments

@rexVictor
Copy link

Hi y'all,

I have an issue with the compose key when using neo layout. The compose sequence stops when pressing Alt Gr/<> aka ISO_LEVEL5_SHIFT. This happens when I use kitty on sway but not in gkx (The gnome console) on sway.
This makes all entries in the compose map requiring LEVEL5 impossible to type.

The issues becomes apparent when using "xkbcli interactive-evdev --layout de --variant neo --enable-compose" on a tty:
The key combo (I use Qwerty notation here): Left Caps + Tab, a,e produces æ.
The combo Left Caps + Tab, Left Shift(press), Left Shift(release), a, e produces also æ i.e. the "accidental" shift press does not terminate the compose sequence.
However, Caps + Tab, Alt Gr(press), Alt Gr(release),a produces immediately an 'a' like the composing was terminated. Pressing 'e' afterward just adds an 'e' as one would expect then.

My guess is that xkb somehow intercepts the Alt Gr or tries to interpret it as part of a sequence instead of a pure shift modifier.
The same happens by the way if instead of "Alt Gr" the key "<>" is used, which are the two LEVEL5_SHIFT keys in neo.

I'd really like to be able to use my whole .XCompose in all applications. Is it possible by just a config change?

Regards

@wismill wismill added the bug Indicates an unexpected problem or unintended behavior label Dec 5, 2023
@wismill
Copy link
Member

wismill commented Dec 5, 2023

I can confirm. See #415 for a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior keysyms
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants