From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: cpitclaudel@gmail.com, theophilusx@gmail.com,
37517@debbugs.gnu.org, fmdkdd@gmail.com
Subject: bug#37517: New rx.el breaks a number of packages - missing symbol rx-submatch-n
Date: Sun, 29 Sep 2019 16:05:15 +0300 [thread overview]
Message-ID: <83a7anfe2c.fsf@gnu.org> (raw)
In-Reply-To: <1C12B392-EC36-4A73-A80A-24F41F9A736B@acm.org> (message from Mattias Engdegård on Sun, 29 Sep 2019 14:57:23 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 29 Sep 2019 14:57:23 +0200
> Cc: 37517@debbugs.gnu.org, cpitclaudel@gmail.com, theophilusx@gmail.com,
> fmdkdd@gmail.com
>
> > We've heard about one such symbol, which you consider internal, but
> > someone else didn't. Why not provide that one symbol right now? If
> > no other symbol is reported, that will be the only one, but I don't
> > see why it should wait for others to be granted that status.
>
> Given that flycheck was rapidly fixed and the single internal function used was tied to their particular rx use (because the old mechanism for extending rx was under-documented, as alluded by Clément), do you still think we need to add rx-submatch-n for the benefit of old flycheck versions?
Yes. It's just one defalias...
next prev parent reply other threads:[~2019-09-29 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 1:45 bug#37517: New rx.el breaks a number of packages - missing symbol rx-submatch-n Tim Cross
2019-09-26 10:01 ` Mattias Engdegård
2019-09-26 10:53 ` Eli Zaretskii
2019-09-26 12:42 ` Mattias Engdegård
2019-09-26 14:28 ` Eli Zaretskii
2019-09-29 12:57 ` Mattias Engdegård
2019-09-29 13:05 ` Eli Zaretskii [this message]
2019-09-29 15:07 ` Mattias Engdegård
2019-09-29 15:17 ` Eli Zaretskii
2019-09-26 14:04 ` Clément Pit-Claudel
2019-09-26 14:33 ` Mattias Engdegård
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=83a7anfe2c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37517@debbugs.gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=fmdkdd@gmail.com \
--cc=mattiase@acm.org \
--cc=theophilusx@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 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.