From: "Mattias Engdegård" <mattiase@acm.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 50136-done@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#50136: 28.0.50; A problem with rx-let expansion
Date: Mon, 23 Aug 2021 20:05:26 +0200 [thread overview]
Message-ID: <4A408FC9-3B89-40D9-9A88-60AA384BF9DC@acm.org> (raw)
In-Reply-To: <87eeak85cw.fsf@web.de>
23 aug. 2021 kl. 18.59 skrev Michael Heerdegen <michael_heerdegen@web.de>:
> Maybe at least one sentence about that this mechanism just performs
> trivial substitution?
I didn't do that now, because I couldn't see how it could be interpreted otherwise (and there's the manual link).
> I find the term "user-defined" distracting, because anybody (including
> library and package developers) is "affected". Apart from that, ok for
> me.
Thank you, changed.
> Didn't try the example, but it looks good.
Thanks for looking at it. Good examples are always hard to write!
> | (eval EXPR) Match the rx sexp from evaluating EXPR at compile time.
>
> can we say "expansion time" instead of "compile time"?
We can, and now do!
Closing; I think we're done here (complain if not).
next prev parent reply other threads:[~2021-08-23 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 13:59 bug#50136: 28.0.50; A problem with rx-let expansion Michael Heerdegen
2021-08-20 14:50 ` Michael Heerdegen
2021-08-20 15:23 ` Mattias Engdegård
2021-08-20 17:21 ` Michael Heerdegen
2021-08-20 18:45 ` Mattias Engdegård
2021-08-21 11:45 ` Michael Heerdegen
2021-08-21 13:02 ` Mattias Engdegård
2021-08-23 10:45 ` Michael Heerdegen
2021-08-23 12:38 ` Mattias Engdegård
2021-08-23 15:20 ` Mattias Engdegård
2021-08-23 16:59 ` Michael Heerdegen
2021-08-23 18:05 ` Mattias Engdegård [this message]
2021-08-21 3:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A408FC9-3B89-40D9-9A88-60AA384BF9DC@acm.org \
--to=mattiase@acm.org \
--cc=50136-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.