4 ms·

I am a fish shell user, but for me the biggest drawback is that a lot of tools rely on updating bashrc as part of installation and some of them don't have an eq

by xkgt 5y ago

I am a fish shell user, but for me the biggest drawback is that a lot of tools rely on updating bashrc as part of installation and some of them don't have an equivalent `config.fish`.

ayushnix 5y ago
> ... a lot of tools rely on updating bashrc as part of installation and some of them don't have an equivalent `config.fish` such as?
- waterhouse 5y ago
  For example, Macports puts its installed binaries into /opt/local/bin (and sbin), and the installation process put this into my .profile: # MacPorts Installer addition on 2016-07-01_at_00:46:04: adding an appropriate PATH variable for use with MacPorts. export PATH="/opt/local/bin:/opt/local/sbin:$PATH" # Finished adapting your PATH environment variable for use with MacPorts. And I had to put the fish equivalent of that into ~/.config/fish/config.fish myself.
  - ayushnix 5y ago
    Umm, you don't need to define your PATH variable in `config.fish`, not unless you make it your default login and user shell. You should keep using bash as your default login and user shell, define your environment variables, like PATH, in your `.bashrc`/`.bash_profile` but use fish as the default shell of your terminal emulator. In that case, fish should pick up the PATH from bash.
    - xkgt 5y ago
      That addresses only the part of setting up PATH variable. Some init scripts go beyond that and have additional code embedded in them (see sdkman, pyenv). These needs separate init scripts for fish users. Just a cursory look at github issues can show how prevalent this issue is: https://github.com/search?q=fish+support&type=issues https://github.com/search?q=fish+support&type=issues
      - ayushnix 5y ago
        Python venv works fine with fish shell for me. But yeah, this is something that'll always be an issue with fish simply because bash is more widely used. Unlike what some people may think, it's not just about the tool itself but its ecosystem as well.

by xkgt 5y ago

I am a fish shell user, but for me the biggest drawback is that a lot of tools rely on updating bashrc as part of installation and some of them don't have an equivalent `config.fish`.

ayushnix 5y ago

> ... a lot of tools rely on updating bashrc as part of installation and some of them don't have an equivalent `config.fish` such as?

waterhouse 5y ago
For example, Macports puts its installed binaries into /opt/local/bin (and sbin), and the installation process put this into my .profile: # MacPorts Installer addition on 2016-07-01_at_00:46:04: adding an appropriate PATH variable for use with MacPorts. export PATH="/opt/local/bin:/opt/local/sbin:$PATH" # Finished adapting your PATH environment variable for use with MacPorts. And I had to put the fish equivalent of that into ~/.config/fish/config.fish myself.
- ayushnix 5y ago
  Umm, you don't need to define your PATH variable in `config.fish`, not unless you make it your default login and user shell. You should keep using bash as your default login and user shell, define your environment variables, like PATH, in your `.bashrc`/`.bash_profile` but use fish as the default shell of your terminal emulator. In that case, fish should pick up the PATH from bash.
  - xkgt 5y ago
    That addresses only the part of setting up PATH variable. Some init scripts go beyond that and have additional code embedded in them (see sdkman, pyenv). These needs separate init scripts for fish users. Just a cursory look at github issues can show how prevalent this issue is: https://github.com/search?q=fish+support&type=issues https://github.com/search?q=fish+support&type=issues
    - ayushnix 5y ago
      Python venv works fine with fish shell for me. But yeah, this is something that'll always be an issue with fish simply because bash is more widely used. Unlike what some people may think, it's not just about the tool itself but its ecosystem as well.