That doesn't work. I think it's because the environment variables that acme sees are those that already existed when it was called, and not those created afterwards.
2011/2/23 Gabriel Diaz <[email protected]>: > hello > > probably there are a better ways, like rc maintainng a `namespace`/env fs, > so it reads that fs creating the environment correspondant to that namespace > when started or simmiliar, but in lunix way (and with other shells) you can > use one script to launch acme that executes the arguments of the Local > script after the acme launch :-? > start_acme.sh > #/bin/bash > acme & > while a=read(named_pipe_or_simmilar); do > $a > done; > > And Local > #!/bin/bash > echo $* > named_pipe_or_simmilar > So Local export var=var could make var available > Also not sure if plumber would help you instead of using pipes. > My corporate pc barely allows me to reply emails, so this is not tested ;) > gabi > > On Wed, Feb 23, 2011 at 11:39 AM, hugo rivera <[email protected]> wrote: >> >> Hello, >> the man page for acme on p9p reads >> >> Local In the Plan 9 acme, this prefix causes a command to be run in >> acme'sown file name space and environment variable group. On >> Unix this is impossible... >> >> is there any other way to define environment variables for acme while >> it's running? >> On plan9, Local var=val sets var and then all other commands I execute >> with a middle click see $var. On some ocasions this is very useful. >> >> -- >> Hugo >> > > -- Hugo
