From: "Mattias Engdegård" <mattiase@acm.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, rajeev@sivalik.com, emacs-devel@gnu.org
Subject: Re: icalendar.el bug fix patch
Date: Fri, 1 Nov 2019 22:38:49 +0100 [thread overview]
Message-ID: <66FE4C1F-B166-42A6-A8EA-C37973072DF7@acm.org> (raw)
In-Reply-To: <34fad408-c220-7980-c7fe-1299093d842f@cs.ucla.edu>
1 nov. 2019 kl. 22.19 skrev Paul Eggert <eggert@cs.ucla.edu>:
> But since the concept is useful, how about if we create an escape for it? For example, we could establish \! as a regexp that matches any single character. This be more readable than either [^z-a] or \(?:.\|
> \), and would surely help performance as well as readability.
Some time ago I experimented with adding a regexp-engine opcode for anychar, but didn't observe any significant difference in performance from that of [^z-a] or \Sq. It is possible that gains could be had if the opcode were to be exploited on a deeper level, such as producing a fast scan loop for [^z-a]*STRING. One has to be careful with backtracking, however.
This is orthogonal to the addition of regexp string syntax for anychar (like \!); neither requires the other.
next prev parent reply other threads:[~2019-11-01 21:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:33 icalendar.el bug fix patch Rajeev Narang via Emacs development discussions.
2019-11-01 9:40 ` Eli Zaretskii
2019-11-01 10:51 ` Mattias Engdegård
2019-11-01 13:00 ` Eli Zaretskii
2019-11-01 11:12 ` Rajeev Narang via Emacs development discussions.
2019-11-01 13:05 ` Eli Zaretskii
2019-11-01 13:24 ` Mattias Engdegård
2019-11-01 13:33 ` Eli Zaretskii
2019-11-01 21:19 ` Paul Eggert
2019-11-01 21:38 ` Mattias Engdegård [this message]
2019-11-02 18:39 ` Juri Linkov
2019-11-03 13:21 ` Richard Stallman
2019-11-03 16:55 ` Drew Adams
2019-11-03 19:55 ` Stefan Monnier
2019-11-03 20:54 ` Juri Linkov
2019-11-03 21:10 ` Stefan Monnier
2019-11-03 21:32 ` Juri Linkov
[not found] ` <E81C3456-834F-469D-B8CA-80B1CDD311F8@acm.org>
2019-11-04 0:50 ` Paul Eggert
2019-11-04 11:56 ` Mattias Engdegård
2019-11-04 15:16 ` Drew Adams
2019-11-03 3:24 ` Richard Stallman
2019-11-03 16:54 ` Drew Adams
2019-11-01 16:44 ` Howard Melman
2019-11-01 14:30 ` 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
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=66FE4C1F-B166-42A6-A8EA-C37973072DF7@acm.org \
--to=mattiase@acm.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rajeev@sivalik.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).