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

Keyd mappings not working with the VSCode integrated terminal #704

Open
karimarttila opened this issue Mar 27, 2024 · 1 comment
Open

Keyd mappings not working with the VSCode integrated terminal #704

karimarttila opened this issue Mar 27, 2024 · 1 comment

Comments

@karimarttila
Copy link

karimarttila commented Mar 27, 2024

Keyd works perfectly with my Linux workstation (Ubuntu 22, Wayland, and Gnome) in terminals and in all applications.
Except in the VSCode integrated terminal.
I have the following code in my /etc/keyd/default.conf file:

capslock = layer(capslock)
[capslock:G]
# Navigation.
j = left
k = down
l = right
i = up

I can use these navigation shortkeys in every other application, and in the VSCode editor view, but not in the VSCode integrated terminal view.

How to examine the issue:

  1. Configure the navigation shortkeys as above.
  2. Start VSCode.
  3. Ctrl+Shift+P (Cmd+Shift+P in Mac) => VSCode command prompt opens, write: Terminal: "Focus on Terminal View" and hit enter.
  4. Integrated Terminal view opens. Try the navigation keys using the integrated terminal. E.g. up/down should give previous / next bash command from the command history.

I'm not sure if this is some feature or bug in the VSCode integrated terminal. In that case, there is nothing to be done and this issue can just be closed.

@karimarttila karimarttila changed the title Keyd mappings not working with the VSCode embedded terminal Keyd mappings not working with the VSCode integrated terminal Apr 7, 2024
@wmertens
Copy link

@karimarttila I just noticed that vscode invisibly remapped the keys at startup when it noticed I had a colemak layout enabled while setting up keyd.

Chording with keyd works for me in the terminal.

There's a debug view for the shortcuts under the command "developer: shortcut troubleshooting" or something along those lines.

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

No branches or pull requests

2 participants