From: "Mattias Engdegård" <mattiase@acm.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
36237@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
kevin.legouguec@gmail.com
Subject: bug#36237: Support (rx (and (regexp EXPR) (regexp-quote EXPR)))
Date: Thu, 20 Jun 2019 12:26:21 +0200 [thread overview]
Message-ID: <FEE9A4AE-B4F6-488D-8C1E-82762BCC5970@acm.org> (raw)
In-Reply-To: <87o92tw13b.fsf@gmail.com>
20 juni 2019 kl. 02.29 skrev Noam Postavsky <npostavs@gmail.com>:
>
> <0001-Support-rx-and-regexp-EXPR-literal-EXPR-Bug-36237.patch>
Things I didn't notice earlier:
-;; (rx (and line-start (eval something-else))), statically or
-;; (rx-to-string '(and line-start ,something-else)), dynamically.
+;; (rx (seq line-start (regexp something-else)))
You can actually drop the `seq' form entirely, since it's implicit in `rx'.
It was only needed for `rx-to-string' which is now gone.
+`(literal STRING)'
+ matches STRING literally, where STRING is any lisp
+ expression that evaluates to a string.
It's better to name the metavariable EXPR, STRING-EXPR or LISP-EXPR to make it clear that it's an arbitrary lisp expression, especially since STRING is used for a constant string just above.
The same goes for `regexp', since it can now be a lisp expression; this should be mentioned in the describing paragraph, using a similar phrasing. The `literal' item should probably be moved next to `regexp', since they are closely related.
The paragraph on `eval' uses FORM, which is too generic; presumably it should become EXPR too (but not STRING-EXPR, since it can be any rx value).
next prev parent reply other threads:[~2019-06-20 10:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 23:43 bug#36237: Support (rx (and (regexp EXPR) (regexp-quote EXPR))) Noam Postavsky
2019-06-16 0:03 ` Michael Heerdegen
2019-06-16 0:28 ` Noam Postavsky
2019-06-16 10:03 ` Mattias Engdegård
2019-06-16 11:34 ` Stefan Monnier
2019-06-16 12:25 ` Noam Postavsky
2019-06-16 12:35 ` Stefan Monnier
2019-06-16 19:50 ` Noam Postavsky
2019-06-16 20:04 ` Stefan Monnier
2019-06-16 20:25 ` Drew Adams
2019-06-16 20:34 ` Mattias Engdegård
2019-06-16 21:09 ` Drew Adams
2019-06-17 20:57 ` Juri Linkov
2019-06-18 19:45 ` Mattias Engdegård
2019-06-19 1:34 ` Noam Postavsky
2019-06-19 15:42 ` Mattias Engdegård
2019-06-20 0:29 ` Noam Postavsky
2019-06-20 10:26 ` Mattias Engdegård [this message]
2019-06-22 22:05 ` Noam Postavsky
2019-06-23 11:09 ` Mattias Engdegård
2019-06-23 15:46 ` Noam Postavsky
2019-06-24 3:50 ` Stefan Monnier
2019-06-24 10:52 ` Mattias Engdegård
2019-06-26 2:07 ` Noam Postavsky
2019-06-23 14:45 ` Drew Adams
2019-06-26 12:23 ` Andy Moreton
2019-06-26 12:56 ` Noam Postavsky
2019-06-26 13:08 ` Andy Moreton
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=FEE9A4AE-B4F6-488D-8C1E-82762BCC5970@acm.org \
--to=mattiase@acm.org \
--cc=36237@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--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).