b925431025
* Give SSH commands the user-level tool paths
ssh host cmd runs neither a login nor an interactive shell, so on Arch it
gets the bare sshd PATH and can't find mise-managed tools like the agent
CLIs herdr scans for. Set PATH in the PAM environment (per-user via
@{HOME}), append the user-level dirs in env-bootstrap so login shells and
the uwsm session get them too, and source env-bootstrap before bashrc's
interactive guard for bash variants that read it non-interactively.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Don't let an empty PATH turn into a cwd entry
Appending with a bare "$PATH:" prefix leaves a leading colon when PATH
is unset, which shells treat as the current directory.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
11 lines
544 B
Bash
11 lines
544 B
Bash
run_logged "$OMARCHY_INSTALL/config/theme-system.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/increase-lockout-limit.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/lockscreen-pam.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/fix-powerprofilesctl-shebang.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/ssh-command-path.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/docker.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/snapper.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/locate.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/enable-services.sh"
|
|
run_logged "$OMARCHY_INSTALL/config/firewall.sh"
|