- cross-posted to:
- lobsters@lemmy.bestiver.se
- cross-posted to:
- lobsters@lemmy.bestiver.se
I’ve done something similiar to this over the years for organization purposes and not having to change much between shells except add a path. You can also add cases that check your shell and do something slightly different if needed.
I still write most scripts for bash, but for interactive use fish is just so much better out of the box.
this is my sticking point with fish. I still need to know bash for writing portable scripts, so its hard to justify scripting in fish.
that’s actually a really good argument for not using either.
Taking a step back discussing shells seems like a never ending hell loop.
Sometimes the only way to win is not to play the game.
Use python and stop being stuck in the distant past.