From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <88b53838-29d8-47b1-9ee7-5c4402d56ecc@email.android.com> From: Giacomo Tesio Date: Mon, 15 May 2017 18:30:57 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="001a113fe4e87aa566054f9294d7" Subject: Re: [9fans] equality sign in Rc Topicbox-Message-UUID: bd8c4dae-ead9-11e9-9d60-3106f5b1d025 --001a113fe4e87aa566054f9294d7 Content-Type: text/plain; charset="UTF-8" Actually a --fu variable is not that useful in Plan 9: % --fu=bar % echo $--fu rc: null list in concatenation % echo "$--fu" rc: null list in concatenation % ls /env '/env/*' /env/--fu ... So rc can create a variable starting with more than one '-', but can't use it. So I wonder if there is a definition of "the right thing" that can fix this incongruence and also allow the UNIX usage. Giacomoec 2017-05-15 17:59 GMT+02:00 Charles Forsyth : > > On 15 May 2017 at 16:54, Erik Quanstrom wrote: > >> if we implement the right thing, then arguments like --fu=bar will be >> 'eaten silently' from the perspective of the (human) operator. sure gigo, >> but this seems extra hard o get right in a Unix environment. > > > It would be better then to leave things as they are. > = is part of rc syntax, like {} and (), and it interprets it, not the > commands, unless quoted. > --001a113fe4e87aa566054f9294d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Actually a --fu variable is not that useful= in Plan 9:

% --fu=3Dbar
% = echo $--fu
rc: null list in concatenation
% echo "$--fu"rc: null list in concatenation
% ls /env
'/env/*'
/env/--= fu
...

So rc can create a variable starting with more than = one '-', but can't use it.

So I wonder if there is= a definition of "the right thing" that can fix this incongruence= and also allow the UNIX usage.


Giacomoec

2017-05-15 17:59 GMT+02:00 Charles Forsyth <charles.forsyth@gma= il.com>:
<= div class=3D"gmail_extra">
O= n 15 May 2017 at 16:54, Erik Quanstrom <quanstro@quanstro.net><= /span> wrote:
if we implement the right t= hing, then arguments like --fu=3Dbar will be 'eaten silently' from = the perspective of the (human) operator. =C2=A0sure gigo, but this seems ex= tra hard o get right in a Unix environment.

It= would be better then to leave things as they are.
=3D is part of rc syntax, like {} and (), and it interprets it, not= the commands, unless quoted.

--001a113fe4e87aa566054f9294d7--