-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
A field in the workspaces window to add extra rules #59
Comments
Couldn't you just add your extra rules to the main config file? |
Oh are you saying, if I will do something like:
The the rules from |
We just include some lines from the workspaces.conf file to the hyprland.conf file. You're free to add whatever afterwards. |
I just tried using nwg-shell. I installed everything, and setup persistent workspaces. I setup binds in hyprland config such that I can switch to those workspaces using split-workspaces. But when I use nwg-shell, I am unable to switch to the empty persistent workspaces even though they show up in the hyprland workspace pager. The same command works just fine with my old config. I checked the same by executing the command from the terminal, that works too. But through the keybind it does not, and only happens with nwg-shell. Any idea why that might happen? |
I have no idea what persistent workspaces are. |
Here is a link which explains persistent workspaces: hyprwm/Hyprland#658. The workspaces have an option |
I think I found the issue, it seems that I am able to change the workspace, but the workspace pager is not getting updated when the workspace is empty and is not next to an occupied workspace. I can try to change the |
Sure, go ahead. Remember to describe your changes. |
Thank you so much for your work on this application. Just the one I was looking for. Though for the workspaces section, I was wondering if it were possible to add an extra field, to enable more flags.
For example, in my case I like to use persistent workspaces on my default monitor. An option to add that would be great!
The text was updated successfully, but these errors were encountered: