Make Hermes follow the Omarchy theme as a skin
(cherry picked from commit 988da12cb0)
(cherry picked from commit 6d3ae7a811ecda54ca11bff0991c2a72878a29e3)
33 lines
1.3 KiB
Bash
Executable File
33 lines
1.3 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Install the Hermes desktop app
|
|
# omarchy:requires-sudo=true
|
|
|
|
set -e
|
|
|
|
# No CLI is installed here on purpose. Hermes Desktop only runs against a
|
|
# runtime built from its own commit, so it provisions one itself under
|
|
# ~/.hermes on first launch, which takes a few minutes and shows its own
|
|
# progress. Handing it the mise CLI instead fails: PyPI trails the tags, and
|
|
# the version gap fails the app's readiness probe with a 401.
|
|
echo "Installing Hermes Desktop..."
|
|
omarchy-pkg-add hermes-desktop
|
|
|
|
# If Hermes was already installed for the terminal, the app supersedes it: one
|
|
# machine, one Hermes. This drops that copy so the terminal, the default agent
|
|
# and the app all end up on the app's installation.
|
|
omarchy-install-hermes-cli || true
|
|
|
|
echo "Opening Hermes Desktop..."
|
|
setsid uwsm-app -- /usr/bin/hermes-desktop >/dev/null 2>&1 &
|
|
|
|
# Only a running Hermes can be told which skin to show, and the first launch
|
|
# takes minutes; a unit outlives this terminal and reports to the journal.
|
|
echo "Matching Hermes to the current theme once it is set up..."
|
|
systemctl --user stop omarchy-hermes-theme.service 2>/dev/null || true
|
|
systemd-run --user --quiet --collect --unit=omarchy-hermes-theme omarchy-theme-set-hermes --wait
|
|
|
|
echo ""
|
|
echo "Hermes Desktop has been installed."
|
|
echo "Its first launch installs the Hermes runtime, which takes a few minutes."
|