From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <9748601494866680@web4g.yandex.ru> References: <9748601494866680@web4g.yandex.ru> From: Charles Forsyth Date: Mon, 15 May 2017 22:02:38 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="001a1140298c115b2d054f96605c" Subject: Re: [9fans] equality sign in Rc Topicbox-Message-UUID: bdbfe592-ead9-11e9-9d60-3106f5b1d025 --001a1140298c115b2d054f96605c Content-Type: text/plain; charset="UTF-8" On 15 May 2017 at 17:44, trebol wrote: > I suppose this is the perfect answer to my silly question: why not permit = > after the start of a command? > do that, but make it behave like = before the start of the command. rc provides the outer syntax for all commands, as it does for file matching and redirection. the commands receive argv[], and (in Plan 9) /env as before. rc puts positional word arguments in argv, which are identified by position, and assignments in /env, which is what it currently does for x=y before a command (or before no command). --001a1140298c115b2d054f96605c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

= On 15 May 2017 at 17:44, trebol <trebol55555@yandex.ru> = wrote:
I suppose this is the perfect answer to my silly quest= ion: why not permit =3D
after the start of a command?

do that, but make= it behave like =3D before the start of the command.
rc provides the outer syntax for all commands, as it does for fil= e matching and redirection.
the commands re= ceive argv[], and (in Plan 9) /env as before.
rc puts positional word arguments in argv, which are identified by posit= ion, and assignments in /env, which is what it currently does for x=3Dy bef= ore a command (or before no command).
--001a1140298c115b2d054f96605c--