9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] equality sign in Rc
Date: Mon, 15 May 2017 18:30:57 +0200	[thread overview]
Message-ID: <CAHL7psEO54aBjgsoNYz-gmzyptqTS7mtVZm3XYngMY1QQwUq_A@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hqZjyCs4Cm8MPYQFgf_fB88ZsZcnneD4Z7JDQLSjq7vA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

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 <charles.forsyth@gmail.com>:

>
> On 15 May 2017 at 16:54, Erik Quanstrom <quanstro@quanstro.net> 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.
>

[-- Attachment #2: Type: text/html, Size: 1750 bytes --]

  reply	other threads:[~2017-05-15 16:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13 12:36 trebol
2017-05-13 13:42 ` Charles Forsyth
2017-05-13 14:21   ` trebol
2017-05-13 16:53     ` Charles Forsyth
2017-05-13 22:41       ` Bruce Ellis
2017-05-14  9:56 ` Charles Forsyth
2017-05-14 15:36   ` trebol
2017-05-14 22:31     ` erik quanstrom
2017-05-15  8:58       ` Charles Forsyth
2017-05-15 11:48         ` trebol
2017-05-15 11:54           ` Charles Forsyth
2017-05-15 11:55             ` Charles Forsyth
2017-05-15 11:56             ` Charles Forsyth
2017-05-15 15:37               ` Erik Quanstrom
2017-05-15 15:42                 ` Charles Forsyth
2017-05-15 15:54                   ` Erik Quanstrom
2017-05-15 15:59                     ` Charles Forsyth
2017-05-15 16:30                       ` Giacomo Tesio [this message]
2017-05-15 16:36                         ` Charles Forsyth
2017-05-15 18:25                           ` Giacomo Tesio
2017-05-15 16:43                         ` trebol
2017-05-15 18:33                           ` trebol
2017-05-15 21:06                             ` Charles Forsyth
2017-05-15 21:48                               ` trebol
2017-05-15 23:38                                 ` trebol
2017-05-15 23:59                                   ` trebol
2017-05-14 22:36     ` trebol
2017-05-14 22:38 ` erik quanstrom
2017-05-15 11:35   ` hiro
2017-05-15 11:45     ` trebol
  -- strict thread matches above, loose matches on Subject: below --
2017-05-15 19:32 sl
2017-05-15 20:15 ` Erik Quanstrom
2017-05-16 17:11 ` Kurt H Maier
2017-05-16 18:27   ` hiro
2017-05-16 18:40   ` Giacomo
2017-05-15 16:44 trebol
2017-05-15 21:02 ` Charles Forsyth
2017-05-16  9:24 ` Charles Forsyth
2017-05-16 15:59   ` Erik Quanstrom
2017-05-16 17:07     ` Giacomo Tesio
2017-05-01 19:27 dexen deVries
2017-05-06  1:53 ` tty0
2017-05-06  7:43   ` Sean Callanan
2017-05-06 13:20     ` Steve Simon
2017-05-06 19:09       ` Sean Callanan
2017-05-06 20:14     ` Nick Owens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHL7psEO54aBjgsoNYz-gmzyptqTS7mtVZm3XYngMY1QQwUq_A@mail.gmail.com \
    --to=giacomo@tesio.it \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).