Replies: 2 comments
|
The reason that command didn't make sense is that mango's tags aren't the same kind of object as i3/Sway workspaces, so there's nothing to "move over" in the way you're picturing. In mango each monitor carries its own tagset, and a window's visibility is tested against its own monitor's tags: uint32_t tagset[2]; // per-monitor, in struct Monitorif (!(c->tags & c->mon->tagset[c->mon->seltags])) // src/fetch/client.hSo "tag 3" isn't one thing living on DP-1 — DP-1 and DP-2 each have their own tag 3, and every window is bound to a monitor ( The command you found is doing two steps because
For moving a tag's contents across, there's no single command, and that follows from the model above — the windows are each bound to a monitor, so it's per-window ( The closest thing to the "one shared set of tags" feel is the The trailing |
|
I'm also interested on this question as mangowc seems to tick all the boxes I have with the exception of this one. I have a 2-monitor + laptop setup that I constantly organise in a way that I have a set of windows on each and when I dock/undock I want that set to continue to behave like a set and eventually come back to the correct monitors when I dock again. i3/sway/hyprland do this by having unique workspaces and then assigning workspaces per monitor Is there any other way mango can map that behaviour? Because moving all windows to a single tag and then having to manually pick them up each is definitely a deal-breaker for this type of workload. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I like Sway/i3 and Xmonad's one set of tags (e.g., 1-9) being shared across multiple monitors. That is, for example, tag 3 is on DP-1 and I can move it with its contents over to DP-2. I thought perhaps Issue #263 was about this, but I'm not sure. And I couldn't figure out the mmsg code identified as the answer:
mmsg -d focusmon,HEADLESS-1 && mmsg -d view,4Is this possible and if so, can someone tell me how?
Thank you for your time and help.
All reactions