9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Fwd: new rc parser
Date: Tue, 05 May 2020 01:08:44 -0400	[thread overview]
Message-ID: <EAEFC596-2E40-4D1A-8913-707C8CE4C9B8@stanleylieber.com> (raw)
In-Reply-To: <CADSkJJU=qQEL4KJLzQXhR3CwuJQmLdZY-EiBQpN5DzGGWbRPgw@mail.gmail.com>




-------- Original Message --------
From: Russ Cox <rsc@swtch.com>
Sent: May 4, 2020 11:57:22 PM EDT
To: plan9port-dev <plan9port-dev@googlegroups.com>
Subject: new rc parser

Hi all,

As an experiment, I have pushed to plan9port a new rc parser
<https://github.com/9fans/plan9port/commit/47d4646eebac34c0b94951cfcf1b81ed2ca513e1>
that resolves two long-time nagging issues:

1. Equal signs (=) are now allowed unquoted
<https://github.com/9fans/plan9port/commit/ff74f7cdda7b08da6fe7c8bbcca990305fd6b547>
in command line arguments.

2. Free carats are now inserted
<https://github.com/9fans/plan9port/commit/7d6a248f2c68d70f58387afc69e73e695c3d940c>
any time two word expressions are next to each other with no spaces, not
just most of the time. For example, the Plan 9 printfont script contains a
bug of the form:

    x=$x'abc'`{def}'ghi'

The bug is that an explicit carat is needed after the }. No longer.

I tested the change by checking every rc script I could find against the
old and new parser; the printfont script mentioned above was the only
affected script (and it's not in plan9port anyway).

You can compare the parser output on any particular script using:

    diff <{rc -Y -D script} <{rc -D script}

If you run into any problems, the old parser is still available using "rc
-Y", but please file an issue so we can fix the new parser.

Best,
Russ

-- 

--- 
You received this message because you are subscribed to the Google Groups "plan9port-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plan9port-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/plan9port-dev/CADSkJJU%3DqQEL4KJLzQXhR3CwuJQmLdZY-EiBQpN5DzGGWbRPgw%40mail.gmail.com.


       reply	other threads:[~2020-05-05  5:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADSkJJU=qQEL4KJLzQXhR3CwuJQmLdZY-EiBQpN5DzGGWbRPgw@mail.gmail.com>
2020-05-05  5:08 ` Stanley Lieber [this message]
2020-05-05  5:49   ` [9front] " ori
2020-05-05 13:00     ` kvik
2020-05-06  7:01       ` jamos
2020-05-05 14:20     ` Stanley Lieber
2020-05-05 15:00       ` hiro
2020-05-05 15:09         ` Stanley Lieber

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=EAEFC596-2E40-4D1A-8913-707C8CE4C9B8@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --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).