4 ms·

"not bash compliant" really is the main deal-breaker. When you're getting technical support on some issue and somebody tells you to paste a command into your te

"not bash compliant" really is the main deal-breaker. When you're getting technical support on some issue and somebody tells you to paste a command into your terminal, "bash compliance" (or at least POSIX-shell compliance) is pretty important. When your phone rings at 2AM and somebody asks you to urgently fix a production problem and you can't figure out what's going on because the production server doesn't have your custom shell installed, that's a problem. It's not a deal-breaker, of course. If you become fluent in POSIX-shell you can translate between it and your custom shell, and things should be fine... but becoming fluent in two shells is a lot more work than becoming fluent in one shell. If you never need to interact with other people's machines, and other people never have to interact with yours, then sure, go nuts and install whatever shell you want.

beaumartinez 13y ago
If you install fish on your local machine, you'll still be able to run bash and punch those commands right into it—just do $ bash And hey presto, back in bash land. I agree that it makes sense to know the lowest common denominator well before you go after something better—especially as you'll know straight away if and why it's "better". Slightly OT, but I honestly think that "community best of" projects like oh-my-zss and the Vim ones actually do people a disservice since they are not zsh or Vim, but rather someone's opinionated, non-standard version of them.
- wging 13y ago
  minor correction: I think you meant to write 'oh-my-zsh' above.
delinka 13y ago
All your executable shell scripts should start with a hash-bang indicating the executable that interprets them. If your script runs on your custom shell and it's not installed, it'll let you know instantly.
deleted 13y ago
[deleted]
mixmastamyk 13y ago
Why assume "install fish" necessitates "uninstall bash"?

beaumartinez 13y ago

If you install fish on your local machine, you'll still be able to run bash and punch those commands right into it—just do $ bash And hey presto, back in bash land. I agree that it makes sense to know the lowest common denominator well before you go after something better—especially as you'll know straight away if and why it's "better". Slightly OT, but I honestly think that "community best of" projects like oh-my-zss and the Vim ones actually do people a disservice since they are not zsh or Vim, but rather someone's opinionated, non-standard version of them.

wging 13y ago
minor correction: I think you meant to write 'oh-my-zsh' above.

delinka 13y ago

All your executable shell scripts should start with a hash-bang indicating the executable that interprets them. If your script runs on your custom shell and it's not installed, it'll let you know instantly.

deleted 13y ago

[deleted]

mixmastamyk 13y ago

Why assume "install fish" necessitates "uninstall bash"?