From: martin rudalics <rudalics@gmx.at>
To: David Koppelman <koppel@ece.lsu.edu>
Cc: Chong Yidong <cyd@stupidchicken.com>,
192@emacsbugs.donarmstrong.com, Bruno Haible <bruno@clisp.org>,
emacs-devel@gnu.org
Subject: Re: regexp does not work as documented
Date: Sun, 11 May 2008 09:40:51 +0200 [thread overview]
Message-ID: <4826A303.3030002@gmx.at> (raw)
In-Reply-To: <yg5bq3ddij2.fsf@nested.ece.lsu.edu>
> First I'll work on the hi-lock warning as I described below, then I'll
> see about detecting and doing something helpful for additional
> situations where multi-line won't work.
Think of the following pathological case: Devise a regexp to highlight
the first line of a buffer provided the buffer does not end with a
newline. Doing this with `font-lock-multiline' hardly makes any sense.
Maybe users should classify whether a regexp they use
(1) doesn't match newlines - no `font-lock-multiline' needed,
(2) match at most n newlines in which case you should tell font-lock to
rescan from n lines before each buffer change (with large n the display
engine will suffer noticeably, mainly because font-lock has to search
for all other keywords as well), or
(3) may match more than n newlines in which case you should use an idle
timer to scan the entire buffer for any matches of such regexps and
highlight them separately.
next prev parent reply other threads:[~2008-05-11 7:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 4:20 regexp does not work as documented Chong Yidong
2008-05-06 11:35 ` Bruno Haible
2008-05-06 12:12 ` martin rudalics
2008-05-10 19:18 ` bug#192: " David Koppelman
2008-05-10 19:18 ` David Koppelman
2008-05-10 20:13 ` David Koppelman
2008-05-11 7:40 ` bug#192: " martin rudalics
2008-05-11 7:40 ` martin rudalics [this message]
2008-05-11 14:27 ` Chong Yidong
2008-05-11 14:27 ` Chong Yidong
2008-05-11 15:36 ` bug#192: " David Koppelman
2008-05-11 15:36 ` David Koppelman
2008-05-11 18:44 ` Stefan Monnier
2008-05-11 19:09 ` David Koppelman
2008-05-12 1:28 ` Stefan Monnier
2008-05-12 15:03 ` David Koppelman
2008-05-12 16:29 ` bug#192: " Stefan Monnier
2008-05-12 16:29 ` Stefan Monnier
2008-05-12 17:04 ` bug#192: " David Koppelman
2008-05-12 17:04 ` David Koppelman
2008-05-12 15:03 ` bug#192: " David Koppelman
2008-05-12 1:28 ` Stefan Monnier
2008-05-11 19:09 ` David Koppelman
2008-05-11 18:44 ` Stefan Monnier
2008-05-11 18:44 ` Stefan Monnier
2008-05-11 20:03 ` Thomas Lord
2008-05-12 1:43 ` bug#192: " Stefan Monnier
2008-05-12 1:43 ` Stefan Monnier
2008-05-12 3:30 ` bug#192: " Thomas Lord
2008-05-12 3:30 ` Thomas Lord
2008-05-12 13:43 ` bug#192: " Stefan Monnier
2008-05-12 13:43 ` Stefan Monnier
2008-05-12 15:55 ` Thomas Lord
2008-05-12 16:18 ` tomas
2008-05-12 16:18 ` bug#192: " tomas
2008-05-12 15:55 ` Thomas Lord
2008-05-11 20:03 ` Thomas Lord
2008-05-11 18:44 ` Stefan Monnier
2008-05-10 20:13 ` David Koppelman
2008-05-06 15:35 ` Stefan Monnier
2008-05-06 21:29 ` Bruno Haible
2008-05-10 20:04 ` Bruno Haible
2008-05-10 20:04 ` bug#192: " Bruno Haible
2008-05-06 15:00 ` David Koppelman
2008-05-06 21:35 ` Bruno Haible
2008-05-07 1:04 ` Stefan Monnier
2008-05-07 1:08 ` Auto-discovery of multi-line font-lock regexps Stefan Monnier
2008-05-07 3:46 ` Chong Yidong
2008-05-07 4:21 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-05-06 1:30 regexp does not work as documented Bruno Haible
2008-05-06 14:15 ` Johan Bockgård
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=4826A303.3030002@gmx.at \
--to=rudalics@gmx.at \
--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 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.