You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw that support for static workspaces was removed in commit 81efd42, can I ask why that decision was taken and if you plan to get it back in the future releases?
I am writing the motivation in-case this feature is not being considered.
I think having static workspaces is very useful, for example I like to have a fixed 10 workspaces on my primary monitor and another 5 on the external monitor. Because I really like to space things out, somehow managing workspaces which are next to each other and also whose workspace number is moving seems hard to handle. If I know that my vscode window is on workspace 10, then I know what shortcut to use to get there. But, now that this number depends on whether I opened or closed more windows in a workspace in between does not make sense. I will now need to open the overview and check for the workspace with vscode each time such a change happens. I do not understand why this is not obvious. This is particularly convenient for example in tiling window managers like BSPWM, Qtile, or i3. Workspaces are not only to separate windows, but also so that I can assign a given workspace for a given task. I can no longer do this with dynamic workspaces, which also makes things inefficient for me.
Is there a better reasoning as to why people do not like fixed workspaces to be implemented? Because even thinking about the overhead for code, I do not see why this would make it more complicated than dynamic workspaces which perhaps needs more routines to add or remove workspaces for every window open/close event.
The text was updated successfully, but these errors were encountered:
saipavanc
changed the title
Support for static workspaces
[Feature request] Support for static workspaces
Dec 30, 2024
I saw that support for static workspaces was removed in commit 81efd42, can I ask why that decision was taken and if you plan to get it back in the future releases?
I am writing the motivation in-case this feature is not being considered.
I think having static workspaces is very useful, for example I like to have a fixed 10 workspaces on my primary monitor and another 5 on the external monitor. Because I really like to space things out, somehow managing workspaces which are next to each other and also whose workspace number is moving seems hard to handle. If I know that my vscode window is on workspace 10, then I know what shortcut to use to get there. But, now that this number depends on whether I opened or closed more windows in a workspace in between does not make sense. I will now need to open the overview and check for the workspace with vscode each time such a change happens. I do not understand why this is not obvious. This is particularly convenient for example in tiling window managers like BSPWM, Qtile, or i3. Workspaces are not only to separate windows, but also so that I can assign a given workspace for a given task. I can no longer do this with dynamic workspaces, which also makes things inefficient for me.
Is there a better reasoning as to why people do not like fixed workspaces to be implemented? Because even thinking about the overhead for code, I do not see why this would make it more complicated than dynamic workspaces which perhaps needs more routines to add or remove workspaces for every window open/close event.
The text was updated successfully, but these errors were encountered: