From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: new rc parser: do we want it?
Date: Wed, 7 Oct 2020 12:02:51 -0700 [thread overview]
Message-ID: <20201007190251.GA197746@alice> (raw)
In-Reply-To: <ABF99C7B10A3BD48F50EB78A213567A4@eigenstate.org>
ori@eigenstate.org once said:
> But mostly, it prevents us from diverging from
> plan9port.
>
> Do we want this?
Yes. I've been using it locally ever since it went into plan9port.
It's a small improvement and I think it's important that rc(1) is
essentially the same everywhere.
Cheers,
Anthony
prev parent reply other threads:[~2020-10-07 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 3:15 ori
2020-10-07 3:54 ` [9front] " sl
2020-10-07 19:02 ` Anthony Martin [this message]
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=20201007190251.GA197746@alice \
--to=ality@pbrane.org \
--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).