From: jan via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 41185@debbugs.gnu.org
Subject: bug#41185: highlight-regexp not working properly for multiline-matching regexps
Date: Wed, 16 Jun 2021 06:20:57 +0100 [thread overview]
Message-ID: <CADJx9LfjwrxOift2=_ky2oXhbYS1GDzfd8rjWL568fuTJAAadQ@mail.gmail.com> (raw)
In-Reply-To: <87tuly66nz.fsf@web.de>
Ach, no, you're right. Tried it in C-mode, was ok.
I think Elil pointed this out in my original bug report about a year
ago and I forgot.
My mistake
jan
On 16/06/2021, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> jan <rtm443x@googlemail.com> writes:
>
>> start emacs with -Q, open a new buffer, say 'asdf'
>
>> type in 'silly'
>>
>> Highlight it; M-s h r silly ret
>>
>> existing silly gets highligted.
>>
>> Press return a couple of times then type in 'silly' again, does not
>> highlight (see silly_twice_only_one_got_highlighted.PNG)
>
> Highlighting is not updated if overlays need to be used because the
> buffer does not use font-lock-mode (see the docstring of
> `highlight-regexp').
>
> Were you aware of that fact, or does your experiment fail even for
> "supported" buffers?
>
>
> Regards,
>
> Michael.
>
prev parent reply other threads:[~2021-06-16 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 11:24 bug#41185: highlight-regexp not working properly jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-11 22:55 ` Michael Heerdegen
2021-06-13 11:37 ` bug#41185: highlight-regexp not working properly for multiline-matching regexps Lars Ingebrigtsen
2021-06-13 16:37 ` Michael Heerdegen
2021-06-13 17:11 ` Lars Ingebrigtsen
2021-06-15 13:25 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-15 23:37 ` Michael Heerdegen
2021-06-16 5:20 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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='CADJx9LfjwrxOift2=_ky2oXhbYS1GDzfd8rjWL568fuTJAAadQ@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=41185@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=rtm443x@googlemail.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.
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).