From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: npostavs@gmail.com, 36496@debbugs.gnu.org
Subject: bug#36496: [PATCH] Describe the rx notation in the lisp manual
Date: Sat, 06 Jul 2019 22:10:38 +0300 [thread overview]
Message-ID: <83zhlr6ksx.fsf@gnu.org> (raw)
In-Reply-To: <BFA06F4B-C7D1-435C-890C-46A3BEA263DA@acm.org> (message from Mattias Engdegård on Sat, 6 Jul 2019 20:56:57 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sat, 6 Jul 2019 20:56:57 +0200
> Cc: 36496@debbugs.gnu.org
>
> >> * lisp/emacs-lisp/rx.el (rx): Replace long description with a condensed
> >> summary of the rx syntax, with reference to the manual section.
> >
> > This is OK, but it is inconsistent wrt whether each construct's
> > description ends in a period. I suggest to end them all with a
> > period.
>
> Added, except at the end of the lists of aliases which looked better with a minimum of punctuation (and weren't sentences to begin with).
It still looks jarring:
+(seq RX...) Match the RXs in sequence. Alias: :, sequence, and
+(or RX...) Match one of the RXs. Alias: |
+
+(zero-or-more RX...) Match RXs zero or more times. Alias: 0+
+(one-or-more RX...) Match RXs one or more times. Alias: 1+
+(zero-or-one RX...) Match RXs or the empty string. Alias: opt, optional
Honestly, they look like incorrect English: a sentence, starting with
a capital letter, but not ending with a period. I hope you will
reconsider.
next prev parent reply other threads:[~2019-07-06 19:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 12:13 bug#36496: [PATCH] Describe the rx notation in the lisp manual Mattias Engdegård
2019-07-04 14:59 ` Drew Adams
2019-07-04 16:28 ` Eli Zaretskii
2019-07-05 14:13 ` Mattias Engdegård
2019-07-06 9:08 ` Eli Zaretskii
2019-07-06 11:33 ` Mattias Engdegård
2019-07-06 11:41 ` Eli Zaretskii
2019-07-06 18:56 ` Mattias Engdegård
2019-07-06 19:10 ` Eli Zaretskii [this message]
2019-07-06 19:45 ` Mattias Engdegård
2019-07-07 2:29 ` Eli Zaretskii
2019-07-07 11:31 ` Mattias Engdegård
2019-07-07 14:33 ` Eli Zaretskii
2022-04-25 15:12 ` Lars Ingebrigtsen
2019-07-06 19:12 ` Noam Postavsky
2019-07-06 11:59 ` Noam Postavsky
2019-07-06 23:56 ` Richard Stallman
2019-07-06 0:10 ` Richard Stallman
2019-07-06 6:47 ` Eli Zaretskii
2019-07-06 23:59 ` Richard Stallman
2019-07-07 0:36 ` Drew Adams
2019-07-07 23:51 ` Richard Stallman
2019-07-08 0:56 ` Drew Adams
2019-07-08 23:46 ` Richard Stallman
2019-07-09 0:19 ` Drew Adams
2019-07-08 23:44 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zhlr6ksx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36496@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=npostavs@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).