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

Many shortcuts don't work with the Neo 2 keyboard layout #1363

Closed
kreibaum opened this issue Apr 4, 2020 · 8 comments
Closed

Many shortcuts don't work with the Neo 2 keyboard layout #1363

kreibaum opened this issue Apr 4, 2020 · 8 comments
Labels
meta: stale This issue/PR is stale and will be closed soon

Comments

@kreibaum
Copy link

kreibaum commented Apr 4, 2020

Describe the bug

When using gitpod with the Neo 2 layout multiple shortcuts don't work. Most prominently, this includes ctrl+S for saving as well as ctrl+C, ctrl+V for copy and paste.

I am on Ubuntu 19.10 and this is a Problem in both Firefox and in Chromium

The layout Neo 2 is a special German layout included with most Linux distributions. I have included an image of the layout to give an idea of its "alien-ness".

Screenshot from 2020-04-05 00-39-46

Steps to reproduce

Use the German Neo 2 layout on Ubuntu and try to save or try to use copy paste in Gitpod.

Expected behavior

I expect those shortcuts to work, as if I where using a standard QWERTZ/QWERTY layout.

Additional information

In vscode there is a bug with Neo 2 where parts of layer 4 don't work (arrow keys on the home row). This must be worked around by setting "keyboard.dispatch": "keyCode" which is not a setting available in Gitpod/Theia. microsoft/vscode#24043

I did not check this with other niche keyboards like Bépo, but I suspect those will have similar issues.

Example repository

I am trying out Gitpod in https://github.com/kreibaum/pacosako but I already had that problem with the animal doctor example project.

@kreibaum kreibaum changed the title Multiple keybindings don't work with the Neo 2 layout Many shortcuts don't work with the Neo 2 keyboard layout Apr 4, 2020
@akosyakov
Copy link
Member

cc @spoenemann

@spoenemann
Copy link
Contributor

spoenemann commented Apr 6, 2020

@kreibaum we need your help to solve this issue. Could you do the following:

yarn --cwd packages/core generate-layout --output src/common/keyboard/layouts/de-Neo_2-pc.json

I know this is quite some work, but there is no way we can fix the issue without a Neo 2 keyboard (I don't have one). Doing these steps on Windows is important so the generated layout data will work on both Linux and Windows. It will not work properly on Windows if you do it on Linux.

@kreibaum
Copy link
Author

kreibaum commented Apr 6, 2020

I think there may be a bit of a misunderstanding about the keyboard. It is a normal German QWERTZ keyboard and I am just using a different layout through software (and blind typing).

Do your comments still apply in that case?

(I can also try to debug what exactly happens in theira if you give me some hints where to start)

@spoenemann
Copy link
Contributor

There's no need to debug, we just need to generate a layout file using the generator script.

You're right, I forgot that it's usually sufficient to set the keyboard layout in the operating system (independently of the actual hardware). In this case someone should check whether the layout is available on Windows, and if yes generate it from there as described above. If not, it's ok to generate it on Linux with the same steps.

@stale
Copy link

stale bot commented Oct 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Oct 4, 2020
kreibaum added a commit to kreibaum/theia that referenced this issue Nov 13, 2020
This is for gitpod-io/gitpod#1363 where I have executed the generate-layout script on an Ubuntu 20.10. (Windows 10 does not support Neo 2 layouts afaik)
@kreibaum
Copy link
Author

Sorry for the delay, I had some problem building it on my machines. I just now got around to setting up a fresh Ubuntu on an older Laptop and here I was able to build theia.

@stale stale bot closed this as completed Mar 18, 2021
@jankeromnes
Copy link
Contributor

Hi @kreibaum, does this issue still reproduce if you switch your IDE to Code in https://gitpod.io/settings/ ? (Under Feature Preview -- but Code will soon become the default IDE in Gitpod)

@kreibaum
Copy link
Author

This is amazing ❤️

It does not work out of the box but the same fix that works for vscode (microsoft/vscode#24043) works in the browser as well.

Thank you for telling me about this new editor frontend!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon
Projects
None yet
Development

No branches or pull requests

4 participants