What happened
omarchy restart terminal (script: /usr/share/omarchy/bin/omarchy-restart-terminal) is documented/expected to reload running terminal emulators after a config change, but its implementation only handles three terminals:
#!/bin/bash
# omarchy:summary=Reload supported terminal emulators after config changes
if [[ -f ~/.config/alacritty/alacritty.toml ]]; then
touch ~/.config/alacritty/alacritty.toml
fi
if pgrep -x kitty >/dev/null; then
killall -SIGUSR1 kitty >/dev/null
fi
if pgrep -x ghostty >/dev/null; then
killall -SIGUSR2 ghostty
fi
There is no branch for foot at all — even though foot is one of Omarchy's default/supported terminals (matched explicitly in default/hypr/apps/terminals.lua, and it's the terminal actually launched by xdg-terminal-exec on a stock/fresh install here). Running omarchy restart terminal after editing ~/.config/foot/foot.ini produces no error and no effect — it silently does nothing for already-open foot windows.
Expected behavior
Either:
- Some indication that foot doesn't support runtime config reload (foot has no reload signal — it only reads config at startup), so the user knows they need to close/reopen windows, or
- At minimum, don't call this a no-op silently — a foot user has no signal that the command did nothing for them.
Steps to reproduce
- Fresh/default Omarchy install where foot is the active terminal (
xdg-terminal-exec resolves to foot).
- Edit
~/.config/foot/foot.ini (e.g. add [colors]\nalpha=0.5 for transparency).
- Run
omarchy restart terminal.
- Observe: command exits with no output/error, but already-open foot windows are unchanged. Only newly launched foot windows pick up the new config.
System details
- Omarchy version: 4.0.2-1
- foot version: 1.27.0 (Jul 21 2026, branch 'makepkg') +pgo +ime +graphemes +toplevel-tag +blur -assertions
- Kernel: Linux 7.1.9-arch1-2 x86_64
omarchy debug --no-sudo --print (as referenced in the project's own contributing docs) is not a recognized command on this version — omarchy commands --all has no debug/diagnostic-log command at all, so I couldn't attach the standard diagnostic log.
Notes
Not asking to add hot-reload support to foot itself (it doesn't have a reload mechanism upstream) — just flagging that the "reload supported terminal emulators" script silently omits foot despite foot being a first-class supported terminal elsewhere in the project.
What happened
omarchy restart terminal(script:/usr/share/omarchy/bin/omarchy-restart-terminal) is documented/expected to reload running terminal emulators after a config change, but its implementation only handles three terminals:There is no branch for foot at all — even though foot is one of Omarchy's default/supported terminals (matched explicitly in
default/hypr/apps/terminals.lua, and it's the terminal actually launched byxdg-terminal-execon a stock/fresh install here). Runningomarchy restart terminalafter editing~/.config/foot/foot.iniproduces no error and no effect — it silently does nothing for already-open foot windows.Expected behavior
Either:
Steps to reproduce
xdg-terminal-execresolves to foot).~/.config/foot/foot.ini(e.g. add[colors]\nalpha=0.5for transparency).omarchy restart terminal.System details
omarchy debug --no-sudo --print(as referenced in the project's own contributing docs) is not a recognized command on this version —omarchy commands --allhas no debug/diagnostic-log command at all, so I couldn't attach the standard diagnostic log.Notes
Not asking to add hot-reload support to foot itself (it doesn't have a reload mechanism upstream) — just flagging that the "reload supported terminal emulators" script silently omits foot despite foot being a first-class supported terminal elsewhere in the project.