aboutsummaryrefslogtreecommitdiff
path: root/sway/AGENTS.md
blob: bb5532ea6509577a1988a81185ca4770017af17d (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

sway — Component Context

Parent rules: ../AGENTS.md (repo root). This package holds the SHARED sway config for every sway-using machine.

The split doctrine

  • Tracked config = shared, machine-agnostic layer: doom-one palette variables, fonts, borders/gaps/titlebars, window rules, ALL muscle-memory key bindings (vim motions, workspaces, screenshots, volume/media/ brightness, resize mode), behavioral QoL. NO exec lines, no machine paths, no output names.
  • Machine overlays: ~/.config/sway/machines/<hostname>.conf, included LAST — they may override anything above and may ONLY contain hardware shape (outputs, input blocks), that machine’s session stack (autostart of its own scripts), lock/idle, and power behavior. NEVER styling. In this repo the pattern is delivered by per-machine packages (currently ../rigel); see machines/README.md for the contract.
  • Sway precedence facts the split relies on: specific output <name> rules beat output *; later bindsym definitions win; include is re-evaluated on every swaymsg reload.

Include depth constraint

Sway’s include is one level deep: machines/*.conf files are included directly by the main config and must NOT themselves contain include.

Session scripts

Referenced autostart scripts are per-machine repo content (rigel package ships its supervisor/fibonacci/ppd/veila helpers). The shared config contains no exec lines, so a bare stow sway on a new machine yields a working, safe desktop before that machine’s overlay lands.