Describe the bug
Pressing ctrl+c on my keyboard does not close the application with svdvorak configured as system layout.
Pressing ctrl+j closes the application. J is where C is on a qwerty keyboard.
To Reproduce
Set your computer to any non-standard layout where C is in the wrong place. Try to exit podman-tui.
Expected behavior
I expect the program to close.
Desktop (please complete the following information):
- OS: Aurora linux, updated as of 28th of may
- Podman Version: 5.8.2
- Podman TUI version 1.11.1 (installed through whatever voodoo ujust-cli does.
Additional context
The keyboard shortcut is probably reading scan codes. It works for most people, since C stays in the same place almost always. Dvorak, french BEPO and latvian ergonomic all have C in the wrong place, and it breaks for them. One work-around for dvorak and french bepo would be to add ctrl j and ctrl x as quit keys (with an "are you sure you want to quit" dialog) if this can't be solved in the "correct" way. This seems very much like it could be an issue with whatever tui framework you are using.
If it is deemed a wont-fix, you could always mention it in the F1 help.
Describe the bug
Pressing ctrl+c on my keyboard does not close the application with svdvorak configured as system layout.
Pressing ctrl+j closes the application. J is where C is on a qwerty keyboard.
To Reproduce
Set your computer to any non-standard layout where C is in the wrong place. Try to exit podman-tui.
Expected behavior
I expect the program to close.
Desktop (please complete the following information):
Additional context
The keyboard shortcut is probably reading scan codes. It works for most people, since C stays in the same place almost always. Dvorak, french BEPO and latvian ergonomic all have C in the wrong place, and it breaks for them. One work-around for dvorak and french bepo would be to add ctrl j and ctrl x as quit keys (with an "are you sure you want to quit" dialog) if this can't be solved in the "correct" way. This seems very much like it could be an issue with whatever tui framework you are using.
If it is deemed a wont-fix, you could always mention it in the F1 help.