fix(install): put ludic on PATH in every shell, not just $SHELL's
The installer edited one profile — whichever ~/.zshrc or ~/.bashrc $SHELL pointed at — and skipped any profile that did not already exist. So a fresh account got nothing written at all, a bash user's ~/.bashrc is not read by the login shell macOS Terminal starts, and ~/.zshrc is only read by interactive zsh. The toolchain installed correctly and `ludic` was still not a command. The PATH edit now lives in one file, <install>/env (plus env.fish), and each profile gets a single line that sources it: ~/.profile for sh and for login bash with no .bash_profile, ~/.zshenv because zsh never reads ~/.profile and reads this one for every invocation, ~/.bashrc and ~/.bash_profile when they already exist, and fish's config when fish is installed. Missing .profile/.zshenv are created; .bash_profile deliberately is not, since creating it would stop bash from reading ~/.profile at all. Sourcing a shared file rather than appending an export keeps a re-install from accumulating a second entry, and leaves one place to delete when uninstalling. Verified with a staged HOME: zsh -i, zsh -c, bash -l, bash -i and sh -l all resolve ludic; a second run reports "already on your PATH" and writes nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
29fcef3b9c
commit
44e752b606
3 changed files with 90 additions and 41 deletions
|
|
@ -42,8 +42,10 @@ formatter and the language server — with one command:
|
|||
curl -fsSL https://workshopsoft.pages.workshopsoft.io/ludic/install.sh | sh
|
||||
```
|
||||
|
||||
It installs into `~/.ludic` and puts `~/.ludic/bin` on your `PATH`; nothing else
|
||||
on the machine is touched, and uninstalling is `rm -rf ~/.ludic`. Where a
|
||||
It installs into `~/.ludic` and puts `~/.ludic/bin` on your `PATH` in every
|
||||
shell — the PATH line lives in `~/.ludic/env`, sourced from `~/.profile`,
|
||||
`~/.zshenv` and your bash or fish config. Nothing else on the machine is touched;
|
||||
uninstalling is `rm -rf ~/.ludic` and deleting those two-line blocks. Where a
|
||||
prebuilt toolchain exists for your platform it is downloaded and verified against
|
||||
a published checksum; where it does not, the installer bootstraps from the
|
||||
compiler's own IR seed with clang. Either way you need clang (or Xcode's Command
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue