unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: jan <rtm443x@googlemail.com>, 41185@debbugs.gnu.org
Subject: bug#41185: highlight-regexp not working properly for multiline-matching regexps
Date: Sun, 13 Jun 2021 18:37:02 +0200	[thread overview]
Message-ID: <874ke1bu1d.fsf@web.de> (raw)
In-Reply-To: <87zgvu3shw.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Sun, 13 Jun 2021 13:37:31 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I can reproduce what the original bug report is seeing -- but that's
> because the regexp seems to be wrong?  There's nothing in the test file
> that matches "# endif".
>
> However the following call does properly match the region I think was
> intended, and works fine, as far as I can see (in Emacs 26.1 and 28):
>
> (highlight-regexp "def HALF_LJ[^^]+?# +endif")
>
> Or do I misunderstand what the original problem was?

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.

Michael.





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

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=874ke1bu1d.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=41185@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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).