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
i3-msg [con_id="id of workspace container"] mark target
i3-msg [con_id="window with focus in screenshot"] move to mark target
W[H|V[H|H]] --> W[H|V[H]|H]
in sway:
workspace can't be marked as it explicitly is not a container.
scenario 2: W[H[H|V[H|H]]]
in i3:
i3-msg [con_id="id of W[H], basically first horizontal container in workspace tree"] mark target
i3-msg [con_id="window with focus in screenshot"] move to mark target
W[H[H|V[H|H]]] --> W[H[H|V[H]|H]]
in sway:
swaymsg [con_id="id of W[H], basically first horizontal container in workspace tree"] mark target
swaymsg [con_id="window with focus in screenshot"] move to mark target
does mark but not move bcs W[H[H|V[H|H]]] is ancestor of W[H[H|V[H|H]]]
my main goal is to move a container from anywhere in the workspace back to workspace level but:
move container to workspace
does nothing when same workspace[con_id=x] mark --add a
does not work on workspace and somove container to mark x
can't be used like it worked in i3my use case: auto layout master stack
problem when: layout T[h|v] and window in h gets closed or moved so T[v] needs become T[h|v]
in i3:
in sway:
proposal (either):
move to workspace
also move the container back to workspace levelThe text was updated successfully, but these errors were encountered: