I'm pretty sure it's possible to configure fish, but I don't feel any need to. That's the good part - works out of box.
However I don't like their new shell syntax, especially env vars handling. Doubt it's configurable.
However I don't like their new shell syntax, especially env vars handling. Doubt it's configurable.
So while you can't do "PATH=$PATH", you could easily make a function that parses that for you, and have "env PATH=$PATH". It's a limitation.
However, it does mean that instead of something like Bash's insanity around P1 when you want a contextual prompt, fish_prompt is a function, with all the beauty of ifs, fors, and whiles spread out in an easy to read language.
Fish can be hit or miss, but it feels like Lua for the shell, to me.