From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: David Koppelman <koppel@ece.lsu.edu>,
192@emacsbugs.donarmstrong.com, Bruno Haible <bruno@clisp.org>,
emacs-devel@gnu.org
Subject: bug#192: regexp does not work as documented
Date: Sun, 11 May 2008 14:44:55 -0400 [thread overview]
Message-ID: <jwv8wygrbss.fsf-monnier+emacsbugreports__30273.0580828667$1210531984$gmane$org@gnu.org> (raw)
In-Reply-To: <87abiwoqzd.fsf@stupidchicken.com> (Chong Yidong's message of "Sun, 11 May 2008 10:27:50 -0400")
> As for making hi-lock-mode detect whether or not a regexp is multi-line,
> isn't that a computationally non-trivial problem?
Well, you can turn the regexp into a DFA, then take the ".*\n.+" regexp,
turn it into another DFA, take the intersection of the two DFAs, and if
it's empty you know your regexp can never match a multiline element.
Stefan
next prev parent reply other threads:[~2008-05-11 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k5i8ukq8.fsf@stupidchicken.com>
[not found] ` <200805061335.11379.bruno@clisp.org>
[not found] ` <48204B3D.6000500@gmx.at>
2008-05-10 19:18 ` bug#192: regexp does not work as documented David Koppelman
[not found] ` <yg5skwqc6ho.fsf@nested.ece.lsu.edu>
2008-05-10 20:13 ` David Koppelman
[not found] ` <yg5bq3ddij2.fsf@nested.ece.lsu.edu>
2008-05-11 7:40 ` martin rudalics
[not found] ` <4826A303.3030002@gmx.at>
2008-05-11 14:27 ` Chong Yidong
[not found] ` <87abiwoqzd.fsf@stupidchicken.com>
2008-05-11 15:36 ` David Koppelman
[not found] ` <yg57ie0df8u.fsf@nested.ece.lsu.edu>
2008-05-11 18:44 ` Stefan Monnier
[not found] ` <jwv4p94r8vp.fsf-monnier+emacsbugreports@gnu.org>
2008-05-11 19:09 ` David Koppelman
[not found] ` <yg5tzh4bqtw.fsf@nested.ece.lsu.edu>
2008-05-12 1:28 ` Stefan Monnier
[not found] ` <jwvr6c8pbd6.fsf-monnier+emacsbugreports@gnu.org>
2008-05-12 15:03 ` David Koppelman
[not found] ` <yg5d4nra7jb.fsf@nested.ece.lsu.edu>
2008-05-12 16:29 ` Stefan Monnier
[not found] ` <jwvzlqvmr6g.fsf-monnier+emacsbugreports@gnu.org>
2008-05-12 17:04 ` David Koppelman
2008-05-11 18:44 ` Stefan Monnier [this message]
[not found] ` <jwv8wygrbss.fsf-monnier+emacsbugreports@gnu.org>
2008-05-11 20:03 ` Thomas Lord
[not found] ` <482750F4.2050102@emf.net>
2008-05-12 1:43 ` Stefan Monnier
[not found] ` <jwvlk2gpas3.fsf-monnier+emacsbugreports@gnu.org>
2008-05-12 3:30 ` Thomas Lord
[not found] ` <4827B9B8.30406@emf.net>
2008-05-12 13:43 ` Stefan Monnier
[not found] ` <jwvfxsnpryp.fsf-monnier+emacsbugreports@gnu.org>
2008-05-12 15:55 ` Thomas Lord
[not found] ` <48286862.6040105@emf.net>
2008-05-12 16:18 ` tomas
[not found] ` <jwvfxsvbgg5.fsf-monnier+emacs@gnu.org>
2008-05-10 20:04 ` Bruno Haible
2008-05-06 1:30 Bruno Haible
2015-12-29 17:48 ` bug#192: " Bruno Haible
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='jwv8wygrbss.fsf-monnier+emacsbugreports__30273.0580828667$1210531984$gmane$org@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=192@emacsbugs.donarmstrong.com \
--cc=bruno@clisp.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=koppel@ece.lsu.edu \
/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).