5 ms·

I used to customise the hell out of tcsh, zsh... until I started using fish, which just has sane defaults.

• RMPR 7y ago
  What makes me reluctant to use fish is the fact that it's syntax is totally incompatible with bash and zsh.
  • fokinsean 7y ago
    Same, I used fish for about a month. I really liked all of it's out of the box features. I reverted back to zsh when everything I googled had to be fish specific and it felt like I was spending more time trying to make bash/zsh instructions work with fish. I do miss the flag suggestions that would autofill.
  • t0astbread 7y ago
    I use fish but only interactively. For scripts I still use bash. The amount of fish-specific syntax I use interactively (and, string interpolation etc.) is so small, it doesn't really bother me. Addendum: I did write my entire prompt (which is 81 lines right now) in fish (my rationale was "maybe it's better performance-wise"), which was hell and I hated it but that's the only piece of fish code I've ever written.
  • dontdieych 7y ago
    you dont need to learn fish syntax for interactive use. basics are almost same. when you met some sh code on random internet, - sh(bash) -c "..." - type bash enter then paste it - save to file + shebang
  • SAI_Peregrinus 7y ago
    https://github.com/edc/bass https://github.com/edc/bass Lets you use bash utilities from fish. So you can do things like `source` files and have it work. Also I prefer to use Fish only as an interactive shell, actual scripts can stay bash.