2 ms·
bass can be helpful for some of those posix issues: https://github.com/edc/bass https://github.com/edc/bass Another random tip: python virtualenv generates a
by dangus 5y ago
bass can be helpful for some of those posix issues:
https://github.com/edc/bass https://github.com/edc/bass
Another random tip: python virtualenv generates a activate.fish script that you should use instead of the plain activate script.
- emptysongglass 5y agoBass has never worked for me, in any scenario. I'm curious to see how you use it. I have never successfully been able to feed it any bash script. At this point I suspect I'm either holding it wrong or it is a thing that is invoked as a thing that works without ever being used in earnest.
- Macha 5y agobass works for things you're meant to source. If the script is not meant to be sourced, just run bash yourscript.sh . It basically runs the script in bash, diffs the environment, and applies the environment changes to your outer fish shell. I use it for some internal tools, and previously used it for nvm though I moved from nvm to fnm now which has fish support.
- yourad_io 5y agoHadn't heard of fnm before, thanks. Seems worth checking out.
- dangus 5y agoIf your bash script has a shebang you shouldn’t need bass at all. Fish will read the shebang and just run your script with bash. The only thing I ever used bass for was this edge case where at work the way we login to AWS is using this Okta AWS integration that prints out a list of export commands. Since fish isn’t compatible with bash export commands, I just run that command result through bass, which automatically converts them to the fish set -x commands. If I remember right, I think the reason why the bash script my company made didn’t work is that the export commands that were run in bash weren’t propagated to the underlying fish environment. I was using fish to run a script with a separate shell, so it didn’t affect my environment variables. Or maybe it was because running exec inside a bash script throws you back into fish which then can’t understand the export command. I could have definitely done my own thing with sed/awk instead, but I suck at those tools and someone else already implemented the functionality in bass. bass exec aws_okta_thing_that_prints_export_commands_to_stdout (Off the top of my head, I think it was something like that, could be misremembering! And by this comment you might be able to tell that I’m far from an expert on how everything works.)
- pxc 5y ago> If your bash script has a shebang you shouldn’t need bass at all. Fish will read the shebang and just run your script with bash. Shebangs are actually handled by the operating system kernel! I only know this because certain kinds of shebangs work on Linux, but not on other OSes