tear-config 0.1.3

Shikumi-style live configuration for the tear multiplexer. Parses ~/.config/tear/tear.yaml, watches it for changes, publishes the parsed TearConfig via Arc<TearConfig> swap. Same configuration story mado uses — operators learn one config style for both apps.
docs.rs failed to build tear-config-0.1.3
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

tear-config — shikumi-style live configuration for tear.

Mirrors the shape mado uses for ~/.config/mado/mado.yaml: a typed [TearConfig] struct deserialized from YAML, made available behind an [arc_swap::ArcSwap] for lock-free reads, refreshed on file-change via notify. Operators set up tear and mado the same way; muscle memory carries.

Layout

~/.config/tear/tear.yaml
─────────────────────────
prefix:        "ctrl+b"        # keybinding prefix (legacy tmux compat)
default_shell: "/bin/zsh"      # spawned in new sessions/windows/panes
mouse:         true            # enable mouse support
base_index:    1               # window numbering start (tmux default 0; many prefer 1)

keys:
  - chord:   "ctrl+a c"
    action:  { kind: new-window }
    note:    "create window"

status:
  refresh_interval_seconds: 5
  left:
    - { kind: text, value: "#[fg=yellow]" }
    - { kind: session-name }
    - { kind: text, value: " · " }
    - { kind: window-name }
  right:
    - { kind: time, format: "%H:%M" }
    - { kind: hostname, short: true }

theme:
  name: nord

Hot reload

[spawn_watcher] kicks off a background thread that re-parses on file mutation. Errors during reload are logged + the previous Arc<TearConfig> stays in place — operators with a syntactically broken file aren't dropped to defaults mid-session.