unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: jan via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 41185@debbugs.gnu.org
Subject: bug#41185: highlight-regexp not working properly for multiline-matching regexps
Date: Tue, 15 Jun 2021 14:25:58 +0100	[thread overview]
Message-ID: <CADJx9Lfz5zrkj8F74_-EbR4mk-=ZdpTXpBatxaXgE_J30mO2+w@mail.gmail.com> (raw)
In-Reply-To: <87zgvt1ygs.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

To reinforce Michael Heerdegen's point, now it seems to be failing on
trivial single-line strings too:

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)

Turn off highlighting (M-s h u) then back on again (M-s h r silly ret)
and both are now highlighted (see silly_both_highlited.PNG), showing
incremental highlighting is indeed failing.

regards

jan

On 13/06/2021, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> I think you must read the original report further, where there is a text
>> example with "endif" for that highlighting fails.  AFAICT the complaint
>> is about multi-line matches not being highlighted.
>>
>> I think `highlight-regexp' is not able to highlight multiline
>> stuff, but the docstring doesn't tell anything about this.
>
> It is being highlit, but not reliably, I see.  If you paste the test
> cases in, they are highlit, but not if you type them in (or paste them
> in in steps)...
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: silly_twice_only_one_got_highlighted.PNG --]
[-- Type: image/png, Size: 7206 bytes --]

[-- Attachment #3: silly_both_highlited.PNG --]
[-- Type: image/png, Size: 7714 bytes --]

  reply	other threads:[~2021-06-15 13:25 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 [this message]
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

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='CADJx9Lfz5zrkj8F74_-EbR4mk-=ZdpTXpBatxaXgE_J30mO2+w@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).