From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: dexen deVries <dexen.devries@gmail.com>
Subject: Re: [9fans] acme Local command on p9p
Date: Fri, 25 Feb 2011 10:32:27 -0500 [thread overview]
Message-ID: <AANLkTi=Pz5vK=NpdR+NT58DScWOGF1OD1Z2SLxXxOL7G@mail.gmail.com> (raw)
In-Reply-To: <201102231835.41505.dexen.devries@gmail.com>
> 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?
plan9port runs in more places than linux.
next prev parent reply other threads:[~2011-02-25 15:32 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
2011-02-25 15:32 ` Russ Cox [this message]
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=Pz5vK=NpdR+NT58DScWOGF1OD1Z2SLxXxOL7G@mail.gmail.com' \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=dexen.devries@gmail.com \
/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).