From: Dale Hagglund <rdh@best.com>
Subject: Re: nnmail-split-header-length-limit is EVIL!
Date: 30 Mar 1999 23:17:07 -0800 [thread overview]
Message-ID: <86bthaf7rg.fsf@ponoka.battleriver.com> (raw)
In-Reply-To: Greg Stark's message of "30 Mar 1999 22:02:32 -0500"
Greg Stark <gsstark@mit.edu> writes:
> Could anyone actually explain why emacs has any trouble running a
> regexp over a few k of text?
As far as I know, this usually results from regexps that have lots of
potential backtracking. You end up with a situation where the
match-time can be exponential in the length of the string being
matched.
I haven't seen any examples of complete regular expressions that cause
the problems we're talking about here, but since they included at
least some user-specified sub-regexps, it might be hard to address the
problem from the regexp side. Do we have any known regexp/string
pairs that deonstrate the problem?
> . . . kludging Gnus to work around it will only let the real bug go
> unfixed longer.
I'm all for fixing it right. My suggested approach is most definitely
a hack, or, in polite company, a heuristic.
Dale.
next prev parent reply other threads:[~1999-03-31 7:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-02 10:57 Hrvoje Niksic
1999-03-06 18:16 ` Lars Magne Ingebrigtsen
1999-03-07 13:27 ` Hrvoje Niksic
1999-03-14 15:53 ` Lars Magne Ingebrigtsen
1999-03-16 7:25 ` Hrvoje Niksic
1999-03-28 15:09 ` Lars Magne Ingebrigtsen
1999-03-29 20:20 ` Hans de Graaff
1999-04-02 14:03 ` Lars Magne Ingebrigtsen
1999-04-03 7:00 ` Hans de Graaff
1999-04-17 6:16 ` Lars Magne Ingebrigtsen
1999-04-13 7:04 ` Hrvoje Niksic
1999-04-17 6:15 ` Lars Magne Ingebrigtsen
1999-03-30 6:05 ` Dale Hagglund
1999-03-31 3:02 ` Greg Stark
1999-03-31 7:17 ` Dale Hagglund [this message]
1999-04-01 2:54 ` Peter Seibel
1999-04-01 7:02 ` Dale Hagglund
1999-04-01 7:13 ` Peter Seibel
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=86bthaf7rg.fsf@ponoka.battleriver.com \
--to=rdh@best.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.
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 NNTP newsgroup(s).