From: David Koppelman <koppel@ece.lsu.edu>
To: martin rudalics <rudalics@gmx.at>
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: Sat, 10 May 2008 15:13:37 -0500 [thread overview]
Message-ID: <yg5bq3ddij2.fsf@nested.ece.lsu.edu> (raw)
In-Reply-To: <yg5skwqc6ho.fsf@nested.ece.lsu.edu> (David Koppelman's message of "Sat, 10 May 2008 14:18:59 -0500")
I *am* able to reproduce the font-lock-multiline limitation martin
described if the buffer is in text mode. I had tried to reproduce it
in emacs-lisp mode.
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.
David Koppelman <koppel@ece.lsu.edu> writes:
> I was able to reproduce the problem with Bruno Haible's testcase and
> font-lock-multiline t does "fix" it. However martin rudalics warns that
> font-lock-multiline won't work for all cases and provides an example
> idea (below). I can't get that to fail. That is, with
> font-lock-multiline t the text was correctly fontified (though after a
> pause). My realization of the example was to remove and then add the
> first quotation mark from one of the interior lines below (also
> tried with more quoted lines):
>
> msgstr ""
> "Project-Id-Version: GNU gettext-tools 0.16.2-pre5\n"
> "Report-Msgid-Bugs-To: bug-gnu-gettext@gnu.org\n"
> "POT-Creation-Date: 2007-11-02 03:23+0100\n"
> "PO-Revision-Date: 2007-10-27 13:35+0200\n"
> "Last-Translator: Christophe Combelles <ccomb@free.fr>\n"
> "Last-Translator: Christophe Combelles <ccomb@free.fr>\n"
> x
>
> The fix I'm contemplating would be to warn the user when a multi-line
> regexp was added interactively and font-lock-multiline was nil, and then
> perhaps to offer to set font-lock-multiline to t (or to not set it, or
> to stop asking).
next prev parent reply other threads:[~2008-05-10 20:13 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 [this message]
2008-05-11 7:40 ` martin rudalics
2008-05-11 14:27 ` bug#192: " Chong Yidong
2008-05-11 14:27 ` Chong Yidong
2008-05-11 15:36 ` David Koppelman
2008-05-11 18:44 ` bug#192: " Stefan Monnier
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 ` Stefan Monnier
2008-05-12 17:04 ` bug#192: " David Koppelman
2008-05-12 17:04 ` David Koppelman
2008-05-12 16:29 ` bug#192: " Stefan Monnier
2008-05-12 15:03 ` David Koppelman
2008-05-12 1:28 ` Stefan Monnier
2008-05-11 19:09 ` David Koppelman
2008-05-11 15:36 ` 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 ` 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-12 3:30 ` Thomas Lord
2008-05-11 20:03 ` Thomas Lord
2008-05-11 7:40 ` martin rudalics
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 ` bug#192: " Bruno Haible
2008-05-10 20:04 ` 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=yg5bq3ddij2.fsf@nested.ece.lsu.edu \
--to=koppel@ece.lsu.edu \
--cc=192@emacsbugs.donarmstrong.com \
--cc=bruno@clisp.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.