- homebrew compatibility on ubuntu
- Python environments
- Vars, expansions, extensions, suffixes
- For loops
- Test exit status
- Temporary variable setting uses
- VS code
- Aliases, custom commands
Not the aquatic creatures, but rather the
which is not as shit as the other ones.
I’m gradually transitioning to
fish, after accidentally losing a lot of precious data due to a quirk in
bash syntax. Long boring story.
It’s time for new, exciting, different stupid errors.
fish has a strong fanbase and an opinionated design.
If you dislike those design opinions, at least you might appreciate it has a
healthy degree of sarcasm in said opinions, which sarcasm is sorely absent from
the drearily earnest nerdview of your typical gnu.org
You might also hold that having any kind of principled opinion is better than the
design-by-accumulation-of-tradition-cruft which structures command-line
Modifying the search PATH
Adding a path? Say it’s
set -gx PATH /usr/local/bin $PATH
set -U fish_user_paths /usr/local/bin $fish_user_paths
Removing a path?
set -gx PATH (string match -v /usr/local/bin $PATH)
🏗 explain the difference between
will depend upon me understanding how the content of
$PATH magically replenishes
itself and the difference between “universal” and ”global” variables.
Modifying any settings with GUI
Put commands in
You can hack fish. Popular plugin management systems exist also.
AFAICT a passable default is oh my fish
curl -L https://get.oh-my.fish | fish
fisher seems to be around too?
curl -sL https://git.io/fisher | source && fisher install jorgebucaran/fisher
It also handles
omf plugins, apparently.
omf install spacefish
It does need the wacky powerline fonts.
sudo apt-get install fonts-powerline
homebrew compatibility on ubuntu
Since I use
fish shell as my default but ubuntu automatically execute s the
bash startup script
.profile on login
I ran into the following errors on login, when it tried to run the
fish init in a
bash: set: -g: invalid option set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...] bash: set: -g: invalid option ...
This is maybe related to an intermittently reported bug in homebrew.
The fix that worked for me was to change the automatically-added line in
.profile to be
eval $(SHELL=bash /bin/brew shellenv)
and to add
eval (env SHELL=fish /bin/brew shellenv)
if you are still using
virtualenv on python you will need
virtualenvwrapper.sh. Or switch to native python3
which is more or less the same thing but works better and doesn’t support
python 2. But if you need to support python 2 at this stage it’s because you are
in some weird enterprise environment with horrid legacy software, so hopefully
you can farm this problem out to the tech support team? Either that or you are barred from using
fish by policy and this is not a problem.
Using anaconda python
You need to do some extra setup to use conda with fish.
~/miniconda3/bin/conda init fish
Or, for older versions,
~/miniconda3/ with the output of
conda info --root
if you used a non-standard install location)
Vars, expansions, extensions, suffixes
For more sophisticated string processing, one defines custom functions (which I never actually do) or use classic subcommands which I do all the time.
for file in (ls *.html) mv $file (basename $file .html).txt end
or expansion via
string, which is harder to
for file in (ls *.html) mv $file (string replace -r "\.html\$" .txt $file) end
while true echo "Loop forever" end
Test exit status
if test $status -eq 0 echo yeah end
To simply execute the second command if the first succeeded the command you want is and, which is hard to google for:
../bin/something.sh foo; and cp foo ~/Dropbox/
Temporary variable setting uses
env FOO=BAR baz.sh