noconnorandClaude Opus 5
9ac198da26
Everything on top of a stock Omarchy 4.0.4-1 install, gathered so a second machine can be brought to the same state: the ~/.config files that actually differ from the shipped defaults, the three hand-built themes, the ten shell plugins pinned to commits, the two custom scripts, two user units, and the /etc drop-ins. install.sh applies it all idempotently, backing up anything it overwrites. capture.sh runs the other way so the repo stays the source of truth rather than a snapshot that rots. indie.herdr-hud's ten local-only commits ship as a git bundle plus a working-tree patch, since they stay off the upstream PR deliberately. Secrets, the dotfiles repo's territory (shell/git/mise), the remote-access stack and aether-managed themes are all scoped out; README says why for each. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
11 lines
539 B
Lua
11 lines
539 B
Lua
-- Extra autostart processes.
|
|
-- o.launch_on_start("my-service")
|
|
|
|
-- Keyboard/mouse sharing with the other Omarchy laptop (lan-mouse).
|
|
-- Runs as a daemon; input only crosses the screen edge once the peer is
|
|
-- activated, so starting it here is inert until Handoff is toggled on.
|
|
-- Superseded by the lan-mouse.service systemd user unit (journald logging,
|
|
-- ordering after the portal, Restart=on-failure). launch_on_start sent both
|
|
-- output streams to /dev/null, which hid every pairing failure.
|
|
-- o.launch_on_start("lan-mouse daemon")
|