Skip to content
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

Support environment variables as command line arguments #11

Open
DRMacIver opened this issue Aug 2, 2018 · 3 comments
Open

Support environment variables as command line arguments #11

DRMacIver opened this issue Aug 2, 2018 · 3 comments
Assignees
Milestone

Comments

@DRMacIver
Copy link

Often what I want to do is I run a command, find it's unreliable, and then run it again with autoclave.

It would be nice if I could do this by just pressing up and putting autoclave at the beginning of the line, but if the command I'm running is FOO=bar ./do-stuff I have to instead write FOO=bar autoclave ./do-stuff. It would be convenient if I could write this as autoclave FOO=bar ./do-stuff.

(I'm aware this is a very petty feature request. You should feel free to ignore it as too high a developer : user effort ratio)

@silentbicycle
Copy link
Owner

So other command line arguments that match the pattern something=something should call setenv before the run loop?

@DRMacIver
Copy link
Author

So other command line arguments that match the pattern something=something should call setenv before the run loop?

Yup, exactly.

@silentbicycle silentbicycle self-assigned this Aug 2, 2018
@silentbicycle
Copy link
Owner

That seems like a good idea. I occasionally rely on make doing something similar.

There shouldn't be any ambiguity between environment variable bindings and other command line options, and any other ambiguities (running a program with = in the name, I guess?) shouldn't be surprising. The implementation should be straightforward. I'll probably add it in the next version.

@silentbicycle silentbicycle added this to the 0.3.0 milestone Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants