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

Control key combinations don't work in non-Latin layouts. #3082

Closed
mooskagh opened this issue Nov 8, 2020 · 2 comments
Closed

Control key combinations don't work in non-Latin layouts. #3082

mooskagh opened this issue Nov 8, 2020 · 2 comments
Labels

Comments

@mooskagh
Copy link

mooskagh commented Nov 8, 2020

I know that has been already reported in #2522, but I'd like to bring it up again, as I believe the severity of the issue is undervalued.

I can understand the argument of having of different mapping for Ctrl+key and Alt+key combinations non-QWERTY latin layouts, but for non-latin (e.g. Cyrillic layouts), the experience is currently broken:

  • It's really hard to use command line (e.g. there's no Ctrl+A to go to the beginning of the line, and Ctrl+W to delete a word)
  • It's not possible to do auto-completion in vim (E.g. Ctrl+N, Ctrl+X), or "find next" (Alt+N), or many other combinations.
  • Emacs is totally unusable (try it)
  • Switching the layout back and forth just to type a control key is a very bad experience (as you may imagine).

Also unlike the non-QWERTY Latin layouts where keys are remapped (which is debatable, but I understand the point), for the case of Cyrillic, those combinations don't send any sequences at all, so this behavior just removes the functionality, not replaces it with something "more correct".

Describe the bug
When the current layout is cyrillic, Control key combinations (Ctrl+W, Ctrl+A, etc) don't work.

To Reproduce
Steps to reproduce the behavior:

  1. Select non-latin keyboard layout, e.g. Russian with:
    setxkbmap -option grp:switch,grp:caps_toggle,grp_led:caps us,ru
  2. Use Caps lock to switch between layouts
  3. Try using Ctrl keys to navigate, e.g. Ctrl+A to go to the beginning of bash line, or try use auto-completion in bash, or try using emacs, or any other editor.

Actual behavior
Ctrl+ key combinations don't work

Expected behavior
Ctrl+ key combinations work

$ kitty --debug-config
kitty 0.19.1 created by Kovid Goyal
Linux cremator 5.9.6-arch1-1 #1 SMP PREEMPT Thu, 05 Nov 2020 21:00:46 +0000 x86_64
Arch Linux \r (\l)
LSB_VERSION=1.4
DISTRIB_ID=Arch
DISTRIB_RELEASE=rolling
DISTRIB_DESCRIPTION="Arch Linux"
Loaded config files: /home/crem/.config/kitty/kitty.conf
Running under: X11

Config options different from defaults:
background           Color(red=18, green=38, blue=55)
bold_font            JetBrains Mono Bold
color1               Color(red=255, green=0, blue=0)
color10              Color(red=59, green=207, blue=29)
color11              Color(red=236, green=200, blue=9)
color12              Color(red=85, green=85, blue=255)
color13              Color(red=255, green=85, blue=255)
color14              Color(red=106, green=227, blue=249)
color2               Color(red=55, green=221, blue=33)
color3               Color(red=254, green=228, blue=9)
color4               Color(red=20, green=96, blue=210)
color5               Color(red=255, green=0, blue=93)
color6               Color(red=0, green=187, blue=187)
color7               Color(red=187, green=187, blue=187)
color8               Color(red=84, green=84, blue=84)
color9               Color(red=244, green=13, blue=23)
cursor               Color(red=240, green=203, blue=9)
font_family          JetBrains Mono
font_size            9.0
foreground           Color(red=255, green=255, blue=255)
italic_font          JetBrains Mono Italic
selection_background Color(red=24, green=52, blue=79)
selection_foreground Color(red=181, green=181, blue=181)
shell                /usr/bin/fish
@mooskagh mooskagh added the bug label Nov 8, 2020
@mooskagh mooskagh changed the title Control key combinations don't work in non-English layouts. Control key combinations don't work in non-Latin layouts. Nov 8, 2020
@kovidgoyal
Copy link
Owner

dup of #606 and #2000

@Jakeroid
Copy link

Here is mine solution. Actually, the idea is the same to map each shortcut for the non-Latin character, but I made automated script to do that.

https://jakeroid.com/blog/kitty-shortcuts-work-only-with-latin-characters-how-to-fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants