Yes, absolutely. Oil has a principled representation of the interpreter state, so it should be easy to write a debugger. (Although note that bash actually has

Yes, absolutely. Oil has a principled representation of the interpreter state, so it should be easy to write a debugger. (Although note that bash actually has a debugger called bashdb, which I didn't know about until recently, and I've never heard of anyone using it.) One intermediate step I would like to take is to provide a hook to dump the interpreter state on an error (set -e). Sort of like a "stack trace on steroids". If anyone is running shell cron jobs in the cloud and would like this, please contact me at andy@oilshell.org. I want to give people a reason to use OSH -- right now there is really no reason to use it, since it is doing things bash already does. But I think a stack trace + interpreter dump in the cloud (like Sentry and all those services) would be a compelling feature. I'm looking for feedback on that. Shell scripts have a very small amount of in-process state, so it should be easy to dump every variable in the program. Also some kind of logging hook might be interesting for cloud use cases.