From mboxrd@z Thu Jan  1 00:00:00 1970
From: trebol <trebol55555@yandex.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <CAOw7k5j5zFse0Mn3jFz_NLwvwTfGK=v2xs11aAy2+oZjqZ2x1A@mail.gmail.com>
References: <3850801494679010@web30j.yandex.ru>
	<CAOw7k5iBGmeSK-5Qko80EoBtKOiVCSvZuoQOgpXjPrdswbhgBQ@mail.gmail.com>
	<5053931494776177@web35j.yandex.ru>
	<e5638d7b51cbc62a5f47c6e14f6eec41@lilly.quanstro.net>
	<CAOw7k5j5zFse0Mn3jFz_NLwvwTfGK=v2xs11aAy2+oZjqZ2x1A@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <7977821494848930@web23g.yandex.ru>
Date: Mon, 15 May 2017 13:48:50 +0200
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
Subject: Re: [9fans] equality sign in Rc
Topicbox-Message-UUID: bd1e07b8-ead9-11e9-9d60-3106f5b1d025

Why? the assignment is after the start of the command, so is not an assignment,
and with the correction of Erik, now rc admit the use of = after the first word
(in the first would be an assignment), so two=2 is just an argument to echo,
exactly 'two='2.

I like this behavior.

trebol

> Given
>
>> broken! one=1 two=2 echo $one $two
>>
>> 1 2
>
> What should the following do?
>
> one=1 echo two=2 $one $two
>
> Disregarding a UNIX historical mistake, I'd expect
> 1 2