You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e400a9e
Browse filesBrowse the repository at this point in the historyBrowse files
fix(install): alias on the already-installed exit only for a local match
When the matching version comes from another install earlier on PATH, the
standalone binary may be older, so its alias would run a different version.
Also scope the troubleshooting note to v0.7.1+ curl installs.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Copy file name to clipboardExpand all lines: docs/docs/reference/troubleshooting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ description: "Fix common Altimate Code installation and runtime issues including
10
10
11
11
**Symptoms:**`altimate-code: command not found` after running `curl -fsSL https://www.altimate.sh/install | bash`.
12
12
13
-
As of v0.7.1 the curl-installed binary is named `altimate`, and installers from before the `altimate-code` alias was added put only that name on PATH. Re-run the installer — it adds `altimate-code` next to `altimate` in `~/.altimate/bin` — or call `altimate` directly:
13
+
As of v0.7.1 the curl-installed binary is named `altimate`, and curl installs from v0.7.1 until the `altimate-code` alias was added put only that name on PATH (v0.7.0 and earlier installed `altimate-code` under `~/.altimate-code/bin` instead). Re-run the installer — it adds `altimate-code` next to `altimate` in `~/.altimate/bin` — or call `altimate` directly:
0 commit comments