bass VS libxo

> I do wish fish could seamlessly convert and run bash scripts on the fly..

It can. With a little help. I use this:

https://github.com/edc/bass

I've been using it for years and most things I need nowadays just work (i.e. have Fish support out of the box).

For all the rest, perhaps give https://github.com/edc/bass a try.

If you're running a script, you can use edc/bass to run it from a fish shell. Fisher is one of the first things I install after fish, then bass, z and a few other helper plugins.

https://github.com/edc/bass

https://github.com/jorgebucaran/fisher

Use bass to drop down to bash from fish :)

https://github.com/edc/bass

As for POSIX, I'll just type bash and do what I need to do, or call a script. You also might want to use the plugin bass, because some programs do not pick up on variables that are set in fish. I think there are other similar plugins, but in my experience bass is the best one. https://github.com/edc/bass

This is an older utility, but still a good one - Bass attempts to make the transition from Bash/Zsh to Fish a little simpler: https://github.com/edc/bass

omf install https://github.com/fabioantunes/fish-nvm omf install https://github.com/edc/bass

I think https://github.com/edc/bass might help?

There are a few ways to work with it, either it simply has "var=val" statements that you could turn into a while read loop that sets variables, or you would need something like bass.

There is no need to change `$SHELL` :-/ you can use Bass (https://github.com/edc/bass) to execute any bash script and it will apply the environment variables to the current fish environment.

> In FreeBSD, this problem was solved with libxo[0]:

Libxo happens to be in the base system, but it is generally available:

* https://github.com/Juniper/libxo

* https://libxo.readthedocs.io/en/latest/

Or make it flexible:

> libxo - A Library for Generating Text, XML, JSON, and HTML Output

* https://github.com/Juniper/libxo/

* https://wiki.freebsd.org/LibXo

Want structure? Ask for JSON or XML and parse. Otherwise it's the regular text output.

Can you trust it? Cli tool output is not exactly stable. I thought that's why libxo exists?

https://github.com/Juniper/libxo

Please consider https://github.com/Juniper/libxo or something even better than that.

That would look a lot like FreeBSD. Many of the FreeBSD userland tools are set up to use the excellent libxo (https://github.com/Juniper/libxo) to allow the user's choice of how things are output.