FISH SHELL GIT AUTO FETCH PLUGIN FULL

It's fast, and it's way better than the built-in Bash reverse history search imo, even though it works basically the same way (it should feel very familiar). I have CTRL+R bound to fuzzy reverse history search via fzf in my Fish config.

FISH SHELL GIT AUTO FETCH PLUGIN FULL

So I don't think this quite solves the issue you describe, which is that if your history was full of convenient Fish one-liners, you wouldn't be able to reuse them in your scripts, because for scripting you prefer Bash.ġ. (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.) 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.īass exec aws_okta_thing_that_prints_export_commands_to_stdout 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 was using fish to run a script with a separate shell, so it didn’t affect my environment variables. 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. 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. 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. Fish will read the shebang and just run your script with bash.

If your bash script has a shebang you shouldn’t need bass at all.

Fish shell git auto fetch plugin