From: Michael Heerdegen <michael_heerdegen@web.de>
To: John Mastro <john.b.mastro@gmail.com>
Cc: 27659@debbugs.gnu.org, Philipp Stephani <p.stephani2@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#27659: 26.0.50; Add string-matched-text: string-match + match-string
Date: Sat, 22 Jul 2017 04:02:47 +0200 [thread overview]
Message-ID: <87h8y544ag.fsf@drachen> (raw)
In-Reply-To: <CAOj2CQRV0jHSXWU75f7nxCeGD_A=-L8zp_CN_4Z=6yWjTXxVAQ@mail.gmail.com> (John Mastro's message of "Fri, 21 Jul 2017 16:28:55 -0700")
John Mastro <john.b.mastro@gmail.com> writes:
> I hope you do - both this and the rx pattern would be nice to have.
I think we should make it so that they have corresponding semantics.
Ideally, without variable binding, Phillip's macro should be eqivalent
to calling rx on the pattern args and then calling Stefan's version. On
top of that, both should add variables and back-references in the same
way. It would be very confusing to add the same thing twice with only
very subtle differences (modulo regexp syntax used).
Michael.
next prev parent reply other threads:[~2017-07-22 2:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 6:13 bug#27659: 26.0.50; Add string-matched-text: string-match + match-string Tino Calancha
2017-07-20 0:54 ` Drew Adams
2017-07-20 1:19 ` Tino Calancha
2017-07-20 19:51 ` Philipp Stephani
2017-07-21 12:29 ` Tino Calancha
2017-07-21 13:34 ` Stefan Monnier
2017-07-21 14:08 ` Tino Calancha
2017-07-21 23:28 ` John Mastro
2017-07-22 2:02 ` Michael Heerdegen [this message]
2017-07-23 20:41 ` Philipp Stephani
2017-07-24 14:30 ` Stefan Monnier
2017-07-22 1:46 ` Michael Heerdegen
2017-07-23 20:45 ` Philipp Stephani
2017-07-23 21:39 ` Michael Heerdegen
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=87h8y544ag.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=27659@debbugs.gnu.org \
--cc=john.b.mastro@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
--cc=tino.calancha@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).