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

Different number of workspaces for each monitor? #19

Open
saipavanc opened this issue May 19, 2024 · 4 comments
Open

Different number of workspaces for each monitor? #19

saipavanc opened this issue May 19, 2024 · 4 comments

Comments

@saipavanc
Copy link

Hi, I have been experiencing issues with split-monitorworkspaces (I will refer to this as spw) as well. Specifically the following, I was looking for a dispatcher for prev which works well, when trying to go to the old used workspace in the current monitor. spw fails to do that. I hope that is fixed, I will just give this a try once I will get to my dual monitor setup.

Also, in my setup I usually have separate number of persistent workspaces on different monitors. Is it possible to have the num_workspaces setting for each monitor separately, maybe using the monitor name?

@shezdy
Copy link
Owner

shezdy commented May 19, 2024

I was looking for a dispatcher for prev which works well, when trying to go to the old used workspace in the current monitor. spw fails to do that. I hope that is fixed, I will just give this a try once I will get to my dual monitor setup.

Going to the previous workspace already works with and without the plugin's dispatchers. Hyprland tracks the previous workspace on each monitor.

Also, in my setup I usually have separate number of persistent workspaces on different monitors. Is it possible to have the num_workspaces setting for each monitor separately, maybe using the monitor name?

I'm not sure I understand why you want to do this? You don't need to use every workspace if you don't want to

@saipavanc
Copy link
Author

Going to the previous workspace already works with and without the plugin's dispatchers. Hyprland tracks the previous workspace on each monitor.

Oh, this definitely did not work for me. I used the following: bind = Super, Tab, split:workspace, prev, and it does not stay in the same monitor.

I'm not sure I understand why you want to do this? You don't need to use every workspace if you don't want to

In my workflow, I like to keep a fixed number of workspaces, so I use persistent workspaces. If that is the case, I will have different number of workspaces on each monitor.

@shezdy
Copy link
Owner

shezdy commented May 19, 2024

previous workspace selection should be fixed in d02a613, i didn't realize it could break depending on the dispatchers used

@shezdy
Copy link
Owner

shezdy commented May 19, 2024

In my workflow, I like to keep a fixed number of workspaces, so I use persistent workspaces. If that is the case, I will have different number of workspaces on each monitor.

If you want to use persistent workspaces with different number per monitor can you not do something like this?

plugin:hyprsplit:num_workspaces = 6

workspace = 1, monitor:DP-1, persistent:true
workspace = 2, monitor:DP-1, persistent:true
workspace = 3, monitor:DP-1, persistent:true
workspace = 4, monitor:DP-1, persistent:true
workspace = 5, monitor:DP-1, persistent:true
workspace = 6, monitor:DP-1, persistent:true

workspace = 7, monitor:DP-2, persistent:true
workspace = 8, monitor:DP-2, persistent:true

workspace = 13, monitor:HDMI-A-1, persistent:true
workspace = 14, monitor:HDMI-A-1, persistent:true
workspace = 15, monitor:HDMI-A-1, persistent:true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants