-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shopt block syntax should accept oil:all #1099
Comments
I think this can be easily fixed by adding some options to the source command. |
I don't recommend it, but you can do this already with something like
or vice versa
What I'd recommend instead is to simply invoke one script from the other. You can invoke an OSH script from and Oil script and vice versa. Using the "$0 dispatch pattern" would probably help. Some more info: https://github.com/oilshell/oil/wiki/OSH-versus-Oil |
This does not seem to be working, in my oilrc:
I got:
Version:
|
Hm that is odd, it does seem like there is an issue using the block syntax Both of these don't cause an error
But adding the block introduces an error. I will look into it |
Ah OK now I see why ... this is more like an oversight than a bug I think that should work so you can interoperate between the two |
How is this implemented? Is this hard coded to consume a block after it, or blocks are a basic type of oil that can be passed around in oil? I personally prefer the second way. |
It's designed as a first class type, and should be part of the However it's not fully exposed to users right now. #1025 is part of it |
This came up here: Because config file evaluation need an implicit |
That is, support an option GROUP with the block syntax. This is #1099. Also fix a BUG where 'shopt -p' didn't respect the option stack.
OK this will be out with the next release! |
Release awhile ago: https://www.oilshell.org/blog/2022/07/release-0.11.0.html |
As title. It would be great if there's some kind of mechanics to make them work together. e.g. through some module mechanics. Therefore user can use oil in their own scripting environment, yet depending on osh scripts from legacy environment.
The text was updated successfully, but these errors were encountered: