From: John Wiegley <jwiegley@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Regexp matching
Date: Mon, 08 Feb 2016 10:57:13 -0500 [thread overview]
Message-ID: <m27fifw5ye.fsf@newartisans.com> (raw)
In-Reply-To: <jwvh9hjfgkw.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Mon, 08 Feb 2016 09:06:49 -0500")
>>>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> - We need to update/replace/rewrite our C-level regexp matching code.
> - Most likely, along the way we may be able to add
> "compiled-regexp" objects. Currently the regexp-compilation is done
> transparently, with a cache to avoid obvious performance issues;
> this works well in most cases, but offering access to compiled-regexps
> could open up a few more options.
> - I'd love it if the new code could provide something like
> `make-regexp-case-insensitive'; either applied to the string-regexp or
> to the compiled-regexp, or maybe as an option to `regexp-compile'.
Agreed on all points. Perhaps we could abuse text properties for this, by
allowing regexps that can be enriched with properties like :case-insensitive t.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-02-08 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 3:40 HowTo: directory-files and friends and case-insensitive match raman
2016-02-06 6:21 ` Marcin Borkowski
2016-02-06 8:06 ` Eli Zaretskii
2016-02-06 16:07 ` raman
2016-02-07 17:46 ` John Wiegley
2016-02-07 19:53 ` raman
2016-02-07 19:57 ` Eli Zaretskii
2016-02-07 21:37 ` raman
2016-02-07 22:15 ` John Wiegley
2016-02-08 14:06 ` Regexp matching (was: HowTo: directory-files and friends and case-insensitive match) Stefan Monnier
2016-02-08 15:57 ` John Wiegley [this message]
2016-02-08 16:21 ` Regexp matching Paul Eggert
2016-02-11 19:01 ` John Wiegley
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=m27fifw5ye.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--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.