> You can force rc to setting a variable only if = is surrounded by spaces,
> like in sh, but then you'll have a lot of problems in plan9/p9p.
nack. disregarding the confusion about spaces, incompatible changes aren't ok.
i've heard the argument that one can't make language progress without brea
On Sun May 14 08:32:47 PDT 2017, trebol55...@yandex.ru wrote:
> > That isn't sh's rule. x=y is fine as an assignment without spaces.
>
> Yes, sorry, in fact I was thinking on the contrary I wrote: don't set a
> variable like in sh.
>
> I like the use of spaces permitted in rc, as I said.
i was
> I see. It seems that you know the code very well. If the variable assignments
> are only before a command, why not permit =
> after the command? Do you know if is there a thought reason for that?
More precisely, "after the start of the command".
> That isn't sh's rule. x=y is fine as an assignment without spaces.
Yes, sorry, in fact I was thinking on the contrary I wrote: don't set a
variable like in sh.
I like the use of spaces permitted in rc, as I said.
> [...] Shell/environment variable assignments appear only before a command, as
On 13 May 2017 at 13:36, trebol wrote:
> You can force rc to setting a variable only if = is surrounded by spaces,
> like in sh, but then you'll have a lot of problems in plan9/p9p.
That isn't sh's rule. x=y is fine as an assignment without spaces.
Shell/environment variable assignments appear