From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Rob Pike Date: Wed, 23 Feb 2011 08:57:00 -0800 Message-ID: Subject: Re: [9fans] acme Local command on p9p To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Cc: Russ Cox Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: b39a7f44-ead6-11e9-9d60-3106f5b1d025 On Wed, Feb 23, 2011 at 5:32 AM, Russ Cox 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=3Dval 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 > > =A0 =A0name=3Dvalue... > =A0 =A0cd directory > > and implement only those. =A0Please 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