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: bug#192: regexp does not work as documented
Date: Sun, 11 May 2008 09:40:51 +0200 [thread overview]
Message-ID: <4826A303.3030002__24005.3205438473$1210493601$gmane$org@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: 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 [this message]
[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
[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='4826A303.3030002__24005.3205438473$1210493601$gmane$org@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 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).