From: Gabriel Diaz <gdiaz@9grid.es>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme Local command on p9p
Date: Wed, 23 Feb 2011 12:21:32 +0100 [thread overview]
Message-ID: <AANLkTi=5HDm142G8MKeWOZ+F8aATXQvreZ6gECWc27tc@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik7uCQ5XyUeANzs-=x4jat2VW-g1-TtwAhrC+My@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
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 <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=val sets var and then all other commands I execute
> with a middle click see $var. On some ocasions this is very useful.
>
> --
> Hugo
>
>
[-- Attachment #2: Type: text/html, Size: 1834 bytes --]
next prev parent reply other threads:[~2011-02-23 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 10:39 hugo rivera
2011-02-23 11:21 ` Gabriel Diaz [this message]
2011-02-23 13:13 ` hugo rivera
2011-02-23 14:34 ` Gabriel Diaz
2011-02-23 13:32 ` Russ Cox
2011-02-23 16:57 ` Rob Pike
2011-02-23 17:09 ` Russ Cox
2011-02-23 17:35 ` dexen deVries
2011-02-25 15:32 ` Russ Cox
2011-02-25 15:44 ` dexen deVries
2011-02-25 15:51 ` roger peppe
2011-02-25 19:01 ` David Leimbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=5HDm142G8MKeWOZ+F8aATXQvreZ6gECWc27tc@mail.gmail.com' \
--to=gdiaz@9grid.es \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).