Feature Request: Set up workspaces per windows Virtual Desktop about glazewm HOT 1 OPEN

Unfortunately I haven't looked too much into the APIs for working with virtual desktops and there's currently some weird behavior when using them. The topic's come up in a discussion before here.

Your use case is definitely valid though and I agree that having a separate set of workspaces on each virtual desktop would be the ideal. However, it's a pretty tough problem to solve. For example, the WM listens for window events like close, minimize, focus, etc., and these aren't isolated to a particular virtual desktop. There'd have to be some way to know which virtual desktop a window belongs to and handle its events accordingly.

If you truly want to approach this problem, one approach would be to change how the ContainerTree (see ContainerService) is structured. Currently, there's a root container with monitors as children, then workspaces, then split containers & windows. To account for virtual desktops, you'd have to a create new container type under the root container for representing a desktop (meaning each desktop has a different set of monitors, workspaces, windows, etc.). Somehow on creation/deletion of a virtual desktop, it'd create/delete the corresponding desktop container (there's an undocumented way to hook into this described here).

Also, do note that you can have more than 9 workspaces - just define more in the user config and assign a keyboard shortcut to switch to that workspace. It does admittedly get pretty awkward defining keyboard shortcuts with that many workspaces though.

from glazewm.