-
Notifications
You must be signed in to change notification settings - Fork 38
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
[BUG] Unable to set a keybinding on Control l #139
Comments
It says it in your screenshot, run Please re-open if it persists |
rofi -list-keybindings just displays all keybindings that are available. It does not provide any information on where the bindings are set. As far as I have found from the rofi documentation, there is a system config file in So the only file where keybindings are set is I moved all custom keybindings to
The issue still persists. |
I somehow fixed this problem but I don't understand how it works. First i checked First I tried to bind I finally tried to bind |
Rofi version (rofi -v or git commit in case of build issue)
1.7.5 wayland3
Configuration
https://gist.github.com/doc-ar/a393b0c1a53bd9ddd8f5a85c026552f0
Theme
https://gist.github.com/doc-ar/a393b0c1a53bd9ddd8f5a85c026552f0
Timing report
No response
Launch command
rofi -show drun -show-icons
Step to reproduce
Step 1
Add the following vim style keybindings to
~/.config/rofi/config.rasi
Step 2
Run rofi launch command
Expected behavior
Rofi runs as usual and i can navigate using the vim style bindings I configured.
Actual behavior
Rofi generates an error window. The error is attached in screenshot
Additional information
For the time being I am using Control semicolon for the next mode keybinding. However it doesn't come very natural since i'm so used to moving right with the L key in vim.
I am using the config and theme file from this repo.
At first I thought that that it might be mapped elsewhere in the configurations. I have checked both the config file and the theme file but control l is not mapped anywhere else.
Just in case I search for all the
.rasi
files usingsudo find / -type f -name "*.rasi"
in my machine and all of them are theme filesUsing wayland display server protocol
I've checked if the issue exists in the latest stable release
The text was updated successfully, but these errors were encountered: