-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
[FEATURE] Export magic variables to env for script execution #1165
Comments
Why not just pass all the needed data as command line arguments? |
I mean sure, but also why not have them as environmental variables? It would decrease the verbosity and make it more clean imho. As a user I was also quite surprised that this doesn't work, which goes against the principle of least astonishment. |
Fair enough. As it turns out, there's not way to access variables in |
Yes that should be supported at least. Even though I think that exporting 10 variables is not all that excessive, one could export just a subset. I mean for the other variables it might not even make sense to be exported, but |
Description of the requested feature
When executing a script from yuck, e.g.
populate its environment with the magic variables beforehand so the script can make use of them. E.g. in my python script I want to do the following:
This will allow to guard against cases where eww is invoked with a specific configuration file (eww --config ...) as described in the docs (if I understood correctly this is why the ${EWW_CMD} variable exists in yuck?).
Proposed configuration syntax
internal
Additional context
No response
The text was updated successfully, but these errors were encountered: