The installers offer to start the daemon at login once it is installed, Enter and -y meaning no, and an uninstall takes the entry back before it removes anything¶
Decision 818 · accepted · 2026-10-09 · issue #76
76 asked whether the daemon-at-login step belongs in the installer. Decision 762 answered¶
that the entry is the daemon's, so an installer that offers it runs troupe-daemon login
on, and that its uninstall should run login off first; neither did. Now both do.
- When. After the daemon is installed and the model settings, under a heading of its
own, before the closing list. The installer asks the installed daemon (
login status) whether an entry is there and where, so the paths stay the daemon's alone: the installers know none of them. - The question is the one
troupe configasks, and Enter is no, as there (762). An entry starts something at every login, so it is written only when somebody says so. - Where an entry is there already, nothing is asked. The installer says where it is
and that
troupe-daemon login offtakes it back. A yes would write the same file again (the entry starts thetroupe-daemona client finds, the installers' shim or the release's own wrapper, both at paths an upgrade keeps), and a no does nothing, so no answer would change anything. It is also why a person who said yes introupe config, which the installer hands over to, is not asked a second time. - The flags are
--start-at-loginand--no-start-at-login(-StartAtLogin,-NoStartAtLogin), each answering without the question. Both together are refused before anything happens, and so is--start-at-loginwith--uninstall. -y(-Yes) alone is not a yes. Decision 682's-yasks nothing and does what the flags name: alone, it installs the daemon and no client. Here, likewise, it turns nothing on, and the step says which command would. A run without a terminal is the same.- A no is nothing, not
login off: an entry already there stays, and the step saystroupe-daemon login onturns it on later. - A refused
login onis a warning with the daemon's reason, and the install stands, as a failed VS Code extension is said rather than thrown. - What the entry starts is left to
login on(762's order:TROUPE_DAEMON_COMMAND, thePATH, the release's wrapper). The installer does not setTROUPE_DAEMON_COMMANDfor the call, so the entry starts what every client on the machine would. - Uninstall.
login offis the first thing done once the plan is agreed, while the daemon that knows where its entry is is still there, before anything is stopped or removed; otherwise the entry would go on starting a program that is gone. The plan names the entry whenlogin statusreports one, andlogin offruns whenever a daemon is installed, because on Linux it also removes the other kind of entry, whichstatusdoes not report. A daemon from beforeloginanswers "unknown arguments" and wrote none, so that answer is passed over in silence. Any other failure is a warning and the uninstall goes on: stopping would leave the entry and the daemon both. --clean-installleaves the entry, since it puts the daemon back where the entry expects it.
Governs: install.ps1, install.sh, scripts/check-installers, scripts/check-installers.ps1