From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 23 Feb 2011 12:21:32 +0100 Message-ID: From: Gabriel Diaz To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd30af68bf734049cf14c1d Subject: Re: [9fans] acme Local command on p9p Topicbox-Message-UUID: b3792862-ead6-11e9-9d60-3106f5b1d025 --000e0cd30af68bf734049cf14c1d Content-Type: text/plain; charset=ISO-8859-1 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 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 > > --000e0cd30af68bf734049cf14c1d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
hello

probably there are a better ways, l= ike rc maintainng a `namespace`/env fs, so it reads that fs creating the en= vironment correspondant to that namespace when started or simmiliar, but in= lunix way (and with other shells) you can use one script to launch acme th= at executes the arguments of the Local script after the acme launch :-?

start_acme.sh
#/bin/bash

=
acme &
while a=3Dread(named_pipe_or_simmilar); do
<= div>=A0 =A0$a
done;


And L= ocal
#!/bin/bash
echo $* > named_pipe_or_simmilar
So Local export var=3Dvar could make var available
<= br>
Also not sure if plumber would help you instead of using pipe= s.

My corporate pc barely allows me to reply emails, so th= is is not tested ;)

gabi


<= div class=3D"gmail_quote">On Wed, Feb 23, 2011 at 11:39 AM, hugo rivera <uair00@gmail.com= > 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=3Dval sets var and then all other commands I execute with a middle click see $var. On some ocasions this is very useful.

--
Hugo


--000e0cd30af68bf734049cf14c1d--