5 ms·

So is the normal usage path to start using osh for interactive use and then use osh in a bash compatible mode to write scripts that are less buggy but can still

So is the normal usage path to start using osh for interactive use and then use osh in a bash compatible mode to write scripts that are less buggy but can still be run on bash? Or is it more common to write scripts that tend to then require the osh runtime exist in whatever context they are deployed to?

chubot 6y ago
Right now, I use osh interactively in a very bash compatible mode. Then at the top of my scripts I put this if I still want to run with bash: shopt -s strict:all 2>/dev/null || true Or this if I don't need to run with bash anymore: shopt --set oil:basic Example: https://github.com/oilshell/oil/blob/master/test/spec.sh#L9 https://github.com/oilshell/oil/blob/master/test/spec.sh#L9 docs in progress: https://www.oilshell.org/release/0.8.3/doc/oil-options.html https://www.oilshell.org/release/0.8.3/doc/oil-options.html Having the OSH runtime exist everywhere is something we should work on: https://github.com/oilshell/oil/issues/463 https://github.com/oilshell/oil/issues/463