From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: regex.c simplification
Date: Thu, 19 Jul 2018 20:33:36 -0400 [thread overview]
Message-ID: <jwvin5asq5q.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 30e30c9d-1e0d-ea7d-2ef5-ae8622875449@cs.ucla.edu
>>> If we wanted to make the fork more official, we could simplify src/regex.c
>>> to not worry about lib-src, by having etags use Glibc/Gnulib regex rather
>>> than Emacs regex.
>> I would welcome such a change.
> I started the ball rolling by writing a patch that changes etags to use
> Glibc regex, falling back on a Gnulib copy if Glibc is not available; see
> Bug#32194. We can follow up later by simplifying the Emacs-only regex code
> to assume Emacs.
I wonder: does etags use regexps internally, or only to handle
user-provided "--regex" arguments?
More specifically, does it come with its own set of hardcoded regexps?
Stefan
next prev parent reply other threads:[~2018-07-20 0:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 15:35 regex.c simplification Daniel Colascione
2018-06-16 15:53 ` Eli Zaretskii
2018-06-16 16:11 ` Paul Eggert
2018-06-16 16:17 ` Daniel Colascione
2018-06-16 18:06 ` Andreas Schwab
2018-06-16 19:27 ` Perry E. Metzger
2018-06-17 16:50 ` Clément Pit-Claudel
2018-06-18 14:08 ` Stefan Monnier
2018-07-17 23:58 ` Paul Eggert
2018-07-20 0:33 ` Stefan Monnier [this message]
2018-07-20 0:59 ` Paul Eggert
2018-07-20 1:42 ` Stefan Monnier
2018-07-20 6:59 ` Eli Zaretskii
2018-07-20 21:49 ` Paul Eggert
2018-07-21 6:43 ` Eli Zaretskii
2018-07-21 7:17 ` Paul Eggert
2018-08-01 0:17 ` Paul Eggert
2018-08-01 2:38 ` Brett Gilio
2018-07-20 6:58 ` Eli Zaretskii
2018-06-16 16:12 ` Daniel Colascione
2018-06-16 16:43 ` Perry E. Metzger
2018-06-16 16:09 ` Noam Postavsky
2018-06-16 16:35 ` Perry E. Metzger
2018-06-16 16:42 ` Daniel Colascione
2018-06-16 16:55 ` Eli Zaretskii
2018-06-16 18:24 ` Perry E. Metzger
2018-06-16 18:29 ` Eli Zaretskii
2018-06-16 18:58 ` Perry E. Metzger
2018-06-16 19:27 ` Eli Zaretskii
2018-06-18 9:36 ` Robert Pluim
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=jwvin5asq5q.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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.