Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Consider shell env var support #263
Right now it's possible to append prefixed additional commands to a block of run/sudo statements with
Naive implementation would simply ape
However, this naive approach would fall down when combined with
would turn into this:
and NOT this, which some users might need/expect:
And because we can't have nice persistent multi-command shell environments, using e.g.
That said, it should definitely be possible to reference the data stored up by
Finally, make sure
Note that I'm using
That said, name suggestions are welcome.
Originally submitted by Jeff Forcier (bitprophet) on 2010-12-01 at 03:11pm EST
Matthew Swasey (mig) posted:
Regarding making sure variables are available to all commands in the pipeline, you could use export or even set automatic exporting, e.g.:
would turn into:
Both these forms are POSIX compliant IIRC (they work in sh, bash, dash, ksh at least) but may not work in all shells (e.g. csh).
on 2010-12-02 at 05:13am EST
Jeff Forcier (bitprophet) posted:
Hah, I had totally forgotten that that's a valid way of doing this, but you're quite right. That would likely simplify the implementation a bit too -- should make it just another special-case of prefix (albeit one where it must always be placed at the beginning of the commands list). Using a Fab env-var dict and
on 2010-12-08 at 01:16pm EST