nebula-project/Nebula-OS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Stop pinning Sway output mode in dev config

Browse Source 
Removes the hardcoded `output * mode 1920x1080` from the development Sway config and updates related docs to match. Dev sessions now rely on each output’s preferred mode at scale `1`, which better follows current display size (including VMware autofit behavior), while still documenting how to set a mode manually when needed.
This commit is contained in:
andrew
2026-08-26 17:51:46 +12:00
parent ab869119cc
commit 8c07c10050
3 changed files with 6 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
shells/desktop/README.md
+2 -2
View File
@@ -218,7 +218,7 @@ QT_QUICK_BACKEND=software ./build/nebula-shell
### Output / resolution
The development Sway config requests `1920x1080` at scale `1` when that mode exists. If the VM does not advertise it, Sway keeps the preferred mode. This is a development default, not a production requirement.
The development Sway config uses scale `1` and does not pin a resolution. Sway uses the output's preferred mode so the session follows the current display size.
Inspect outputs and modes:
@@ -229,7 +229,7 @@ swaymsg -t get_outputs
Set a mode explicitly if needed:
```bash
swaymsg output <name> mode 1920x1080
swaymsg output <name> mode 1600x900
swaymsg output <name> scale 1
```