Tenacious B (twoot.site edition) on Nostr: Alright, here's probably the easiest way to test the next fish release:cargo install ...
Alright, here's probably the easiest way to test the next fish release:cargo install --git https://github.com/faho/fish-shell --branch fish-installer~/.cargo/bin/fish --install~/.cargo/bin/fish
and to uninstall:cargo uninstall fish; rm -r ~/.local/share/fish/install
This will give you a separate, per-user fish installation. It will read your config but will have its own separate data files.
Things I know don't work yet:<li><code>man builtin</code> / <code>builtin --help</code> - the man pages aren't hooked up</li><li><code>help builtin</code> sends you to a link that doesn't exist yet (this would be fixed by making a release, uploading in-progress docs or messing with the link)</li><li><code>printf %f</code> lost a slight amount of precision on 32-bit machines</li><li>this install has the building user's $HOME hardcoded for the data path, so moving it elsewhere won't work</li>
and to uninstall:cargo uninstall fish; rm -r ~/.local/share/fish/install
This will give you a separate, per-user fish installation. It will read your config but will have its own separate data files.
Things I know don't work yet:<li><code>man builtin</code> / <code>builtin --help</code> - the man pages aren't hooked up</li><li><code>help builtin</code> sends you to a link that doesn't exist yet (this would be fixed by making a release, uploading in-progress docs or messing with the link)</li><li><code>printf %f</code> lost a slight amount of precision on 32-bit machines</li><li>this install has the building user's $HOME hardcoded for the data path, so moving it elsewhere won't work</li>