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

Default mapping for rotating selection's content backward doesn't work with German keyboard #4082

Closed
jtrees opened this issue Mar 2, 2021 · 7 comments
Labels

Comments

@jtrees
Copy link

jtrees commented Mar 2, 2021

Steps

  1. Have the following three selections: a, b, c
  2. Try to rotate their contents backward (with <alt>+<shift>+8)

Outcome

register '/' set to 'a|b|c'

Expected

The selection contents should be rotated, resulting in c, a, b.

Notes

  • keyboard layout is German
  • kakrc is empty
  • version: Kakoune v2020.09.01-217-g14f7d263
  • kitty terminal emulator
  • rotating contents forward (with <alt>+<shift>+9) works
@jtrees jtrees added the bug label Mar 2, 2021
@lenormf
Copy link
Contributor

lenormf commented Mar 2, 2021

@Screwtapello
Copy link
Contributor

Outside of Kakoune, what gets printed when you run cat and press <a-(> ?

@jtrees
Copy link
Author

jtrees commented Mar 2, 2021

Outside of Kakoune, what gets printed when you run cat and press <a-(> ?

If I press <a-(> I get ^[*. Pressing <a-)> (which appears to work as intended) results in ^[(.

I didn't know this trick.

@jtrees
Copy link
Author

jtrees commented Mar 2, 2021

I think you have the primitive mixed up:

How so?

@mawww
Copy link
Owner

mawww commented Mar 3, 2021

^[* means <a-*> which is what I'd expect from a regular qwerty keyboard where * is Shift+8, this seems to match with ^[( you get by pressing Alt+Shift+9. Are you confided your configuration actually sets the keyboard layout to german ?

@Screwtapello
Copy link
Contributor

Even if the keyboard layout is configured correctly at the OS level, Kitty may be incorrectly mapping keycodes to the terminal encoding.

@jtrees
Copy link
Author

jtrees commented Mar 3, 2021

Even if the keyboard layout is configured correctly at the OS level, Kitty may be incorrectly mapping keycodes to the terminal encoding.

Wow. That is most likely what's going on. I tried the cat thing in elementary Terminal (I'm on elementary OS) and sure enough: <a-(> gives me ^[( and <a-)> gives me ^[). So it's either a config thing or a Kitty bug.

Thanks!

EDIT: Sure enough. This comment led me to try the current master branch of kitty where the issue appears to have been fixed.

@jtrees jtrees closed this as completed Mar 3, 2021
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

4 participants