Proposal: Optional Global Workspace Mode for Multi‑Monitor Setups #8412
amacieli
started this conversation in
Suggestions
Replies: 1 comment
|
COSMIC DE also has "Workspaces span multiple displays" and "Displays have separate workspaces" options. Workspaces spanning multiple displays really ought to be an option for Omarchy if it is at all feasible. Not having this option significantly reduces the benefit of having multiple displays, for many people. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
I’m working with a 3‑monitor setup (maybe 4 if I get my extra suppor), and the current per‑monitor workspace model makes it difficult to treat all displays as a single unified workspace. A global mode would allow multi‑monitor users to keep different full-screen layouts in different workspaces, which is a common workflow in tiling WMs like Sway, i3, and Hyprland.
Omarchy’s current workspace behavior is per‑monitor: workspace 1 is tied to monitor 1, workspace 2 to monitor 2, etc. This works well for single‑monitor setups, but on multi‑monitor systems it can feel unintuitive because switching to workspace N only affects one monitor.
I’d like to propose an optional “Global Workspace Mode” that preserves the existing behavior by default but allows users to opt into a global model where all monitors switch together.
Motivation
For multi‑monitor workflows, it’s often desirable to treat all displays as part of a single workspace. In this model:
<special>-Nswitches all monitors to workspace N.This would make Omarchy more flexible without changing its default behavior.
Proposed Design (minimal impact)
Introduce a configuration option:
workspace_mode = "local" # current behavior (default)
workspace_mode = "global" # new optional behavior
When
workspace_mode = "global":<special><alt>-Nmoves the focused window to workspace N (same monitor).When
workspace_mode = "local":Low‑risk change, because:
References
This feature is conceptually similar to:
global_workspacesoptionRequest
If this direction seems acceptable, I’d be happy to prepare a small, incremental PR implementing:
workspace_modeconfig optionI’d be aiming for a minimal diff by isolating global workspace logic behind a configuration flag and leaving the existing local workspace behavior untouched. The goal is to add functionality without increasing maintenance burden.
Please let me know if this proposal doesn't align with Omarchy’s design goals.
All reactions