9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] new rc parser: do we want it?
Date: Wed, 07 Oct 2020 11:00:19 +0100	[thread overview]
Message-ID: <5a0631b1-afb2-45ea-9250-7eaaf0a31b91@www.fastmail.com> (raw)
In-Reply-To: <1975289B8C108B2FCF360524D16AA25B@ewsd.inri.net>

On Wed, Oct 7, 2020, at 4:54 AM, sl@stanleylieber.com wrote:
> > and unquoted '=' is allowed after the
> > first word:
> >
> > echo a=b
> 
> fwiw, when aiju suggested this a couple years ago i made a
> big stink about how this breaks the predictable quoting
> rules, but if rsc is dispensing with regularity, i don't
> know what to say anymore.  i suppose it's just one more thing to
> remember.

"this breaks the predictable quoting rules" has me a little concerned, but i'm not sure how it does. '=' behaves differently on either side of the first non-assignment word anyway. in the way i look at it, there's nothing to lose; it's already irregular. ;)

even if i'm wrong about that, i'd still be in favour of the change because the old way means urls typically break the convenience of 'send'. at one time, this was a big issue for me. still, my 9front use has dropped to nil, so my opinion's worth nothing unless anyone else feels the same. thinking about it just develops my forth ideas. i've got regular syntax, i can turn the rest of the line into a string and keep it on the stack to work with send (or even pull in the clipboard directly), but optional arguments are not so easy. ;) the fix is probably to break things down into even smaller parts.


       reply	other threads:[~2020-10-07 10:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1975289B8C108B2FCF360524D16AA25B@ewsd.inri.net>
2020-10-07 10:00 ` Ethan Gardener [this message]
     [not found] <5EF01FE4B564E504DD635D7E391EE0C8@ewsd.inri.net>
2020-10-12 20:44 ` Romano
2020-10-15 10:11   ` Ethan Gardener
2020-10-15 12:11     ` Stanley Lieber
2020-10-15 16:41       ` Romano
2020-10-15 17:22       ` Anthony Martin
2020-10-15 23:14         ` Roman Shaposhnik
2020-10-15 23:32           ` Stanley Lieber
     [not found] <01DB736907F1AF8292BF2D9C25564677@ewsd.inri.net>
2020-10-07  4:46 ` ori
2020-10-07 13:06   ` kvik
2020-10-07  3:15 ori
2020-10-07  3:54 ` [9front] " sl

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=5a0631b1-afb2-45ea-9250-7eaaf0a31b91@www.fastmail.com \
    --to=eekee57@fastmail.fm \
    --cc=9front@9front.org \
    /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).