-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Feature] Tag windows to multiple named workspaces #41
Comments
I think of this as a more advanced version of sticky. Marking a view sticky simply means that it appears on all workspaces. You could do this in a plugin where you can match one or more views to be on multiple workspaces. It could assign workspace names such as workspace_# for the convenience of making a comma separated list in wayfire.ini. (I don't know how specifying multiple workspaces using x,y values would work in wayfire.ini but I don't think the syntax would be very nice.) There could perhaps be a way for other plugins like dbus to setup the options so you could assign the workspaces on the command line but it wouldn't be added to config so it would have to be setup again when wayfire restarts. |
I believe tagging window managers don't work this way. It is more like this: Views and outputs both have a set of tags, and on an output, the visible views are these that have at least one of the output's tags. |
You can set a view as sticky but it will show up on all workspaces. If one wants a truly tagging wm, sticky views are not the way to do it - you'll need to not use core's workspaces but implement workspaces/tags entirely in-plugin (sticky views were never blocking this). Of course if you have workspaces like that then also plugins like cube and expo don't make sense anymore .. |
So instead of moving a window to a particular workspace, you tag it with the workspace's name and it appears on all the workspaces it's tagged to.
This naturally implies named workspaces.
Windows could be tagged by calling a program that would tag the focused window.
The text was updated successfully, but these errors were encountered: