From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <88b53838-29d8-47b1-9ee7-5c4402d56ecc@email.android.com> References: <88b53838-29d8-47b1-9ee7-5c4402d56ecc@email.android.com> From: Charles Forsyth Date: Mon, 15 May 2017 16:59:45 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="001a1140458ad9bd5c054f9224fb" Subject: Re: [9fans] equality sign in Rc Topicbox-Message-UUID: bd7eef38-ead9-11e9-9d60-3106f5b1d025 --001a1140458ad9bd5c054f9224fb Content-Type: text/plain; charset="UTF-8" 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. --001a1140458ad9bd5c054f9224fb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

= On 15 May 2017 at 16:54, Erik Quanstrom <quanstro@quanstro.net>= wrote:
if we implement the right = thing, then arguments like --fu=3Dbar will be 'eaten silently' from= the perspective of the (human) operator. =C2=A0sure gigo, but this seems e= xtra 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 c= ommands, unless quoted.
--001a1140458ad9bd5c054f9224fb--