# Role: desktop (beastix - Arch, KDE, X11)
#
# Everything here is either about running a graphical session or about things
# only this machine has. None of it belongs on a headless server or a Mac.

# Qt tries wayland first and falls back to xcb, which covers both session types
# without having to know which one is running.
export QT_QPA_PLATFORM="wayland;xcb"
export MOZ_ENABLE_WAYLAND=1

# The previous configuration exported XDG_SESSION_TYPE=x11 and then, six lines
# later, tested it for "wayland" to decide whether to enable MOZ_ENABLE_WAYLAND.
# That branch could never be taken. XDG_SESSION_TYPE is set by the session
# itself and overriding it lies to everything that reads it, so it is left
# alone; MOZ_ENABLE_WAYLAND is simply set once, above.

export MUTTER_DEBUG_KMS_THREAD_TYPE=user

# Steam prefixes for Path of Exile, used by the trade tooling.
export poe2="$HOME/.local/share/Steam/steamapps/compatdata/2694490/pfx/drive_c/users/steamuser/My Documents/My Games/Path of Exile 2/"
export poe="$HOME/.local/share/Steam/steamapps/compatdata/238960/pfx/drive_c/users/steamuser/My Documents/My Games/Path of Exile/"

# Signal needs a secrets service, and KDE does not start gnome-keyring itself.
#
# This used to exist twice: once here and once as a local custom oh-my-zsh
# plugin named signal-keyring, so it ran on every shell start in both places.
# The plugin is not in this repository and does not exist on the other two
# machines, where naming it in the plugin list produced a warning at every
# login. Keeping the inline version and dropping the plugin fixes both.
if ! pgrep -f gnome-keyring-daemon >/dev/null; then
  eval $(gnome-keyring-daemon --start --components=secrets)
  export $(gnome-keyring-daemon --start --components=secrets | grep ^SSH_AUTH_SOCK)
fi

# Toolchains that only this machine carries.
for _d in "$HOME/.cargo/bin" "$HOME/.lmstudio/bin"; do
  [[ -d "$_d" ]] && case ":$PATH:" in *":$_d:"*) ;; *) PATH="$_d:$PATH" ;; esac
done
unset _d
export PATH

# Role colour, set here rather than in 05-prompt.zsh because ~/.p10k.zsh
# assigns POWERLEVEL9K_CONTEXT_BACKGROUND itself and is sourced in 30-path.zsh.
# Anything set before that is silently replaced. Not decoration: shron carries
# mail, web and cloud, and a glance should say which machine this is.
typeset -g POWERLEVEL9K_CONTEXT_BACKGROUND=blue