From: dexen deVries <dexen.devries@gmail.com>
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 18:35:41 +0100 [thread overview]
Message-ID: <201102231835.41505.dexen.devries@gmail.com> (raw)
In-Reply-To: <AANLkTik9Mf8w9cHq136T=DN=hYFmH+zHZLuXc=drdzTr@mail.gmail.com>
On Wednesday 23 of February 2011 18:09:42 Russ Cox wrote:
> > I'm unsure if this conversation is about Plan 9 or plan9port, but in
> > any case I've used Local for lots of other things on Plan 9,
> > particularly name space manipulations. There, I don't understand why
> > it needs restrictions.
> >
> > Or are you just saying that on plan9port you need to do magic so you
> > might as well catalog the tricks? In that case, I understand.
>
> Yes, the idea is that on plan9port you might change
> the implementation of Local to pick off var=value
> and cd path and run those internally. It could still
> shell out for other commands like Local echo $foo.
How about reading /proc/$pid/environ (where $pid is the shell spawned for
command execution) before the $pid exits and transfering all the environment
variables back to the Acme's own environment?
I'm not sure, but I think that /proc/$pid/environ should be accessible for
Acme after exit() by the $pid, but before Acme's waitpid($pid, ...) completes.
--
dexen deVries
[[[↓][→]]]
> how does a C compiler get to be that big? what is all that code doing?
iterators, string objects, and a full set of C macros that ensure
boundary conditions and improve interfaces.
ron minnich, in response to Charles Forsyth
http://9fans.net/archive/2011/02/90
next prev parent reply other threads:[~2011-02-23 17:35 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
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 [this message]
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=201102231835.41505.dexen.devries@gmail.com \
--to=dexen.devries@gmail.com \
--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).