From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: Russ Cox <rsc@swtch.com>
Subject: Re: [9fans] acme Local command on p9p
Date: Wed, 23 Feb 2011 08:57:00 -0800 [thread overview]
Message-ID: <AANLkTi=GAh3ZudG7yache-Xg1+=rYCDdD-_E2ZSaGuzH@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimtRMQ0_iicjp2XPOTAVpD9BWm+izXp+RTDAY9S@mail.gmail.com>
On Wed, Feb 23, 2011 at 5:32 AM, Russ Cox <rsc@swtch.com> wrote:
>> 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.
>
> It might be a good idea to change the implementation of Local
> to look for the two forms
>
> name=value...
> cd directory
>
> and implement only those. Please file an issue.
>
> Russ
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.
-rob
next prev parent reply other threads:[~2011-02-23 16:57 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 [this message]
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=GAh3ZudG7yache-Xg1+=rYCDdD-_E2ZSaGuzH@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=9fans@9fans.net \
--cc=rsc@swtch.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).