-
Notifications
You must be signed in to change notification settings - Fork 17
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
Navigate workspaces with keybinds? #46
Comments
@cenunix, yes, you can do this with the default bindings of Hyprland:
In my case I have mapped the bracket keys to switch workspaces:
These will work within the overview plugin as well. |
It might be nice if a single hotkey comination could respond to the overview visibility state |
Opening overview does not disable any keybinds in your config, just configure hyprland keybinds to switch workspace.
Yeah that is possible but I could not think of a non-janky way of implementing it atm. |
I was thinking of a separate dispatcher (perhaps overview:openOrNext) that does something like this pseudo-code
No idea if that's how a plugin function is structured but you get the idea, doesn't seem too janky |
The proper way to implement this would be to create a keybind that executes a script that executes different dispatchers based on the overview state. Currently hyprland does not implement any API that allows plugin to interact with external scripts/programs. I might be able to create a socket so that scripts could implement an |
You're right, that would be the more modular solution to this |
Just to add to this - is there a way to get:
to actually move to the next with each subsequent Almost like alt tab at that point. Thank you. Thank you. |
That's discussed above |
Is there any way to navigate through workspaces in the overview with keybinds instead of using the mouse? the mouse controls are nice when my hand is already there, without it already there though I find myself wishing I could scroll back and forth through the previews with a simple keybind.
The text was updated successfully, but these errors were encountered: