From: Michael Heerdegen <michael_heerdegen@web.de>
To: jan <rtm443x@googlemail.com>
Cc: 41124@debbugs.gnu.org
Subject: bug#41124: 26.3; highlight regexp not working properly - not updating as you type
Date: Fri, 08 May 2020 01:20:22 +0200 [thread overview]
Message-ID: <877dxn8h8p.fsf@web.de> (raw)
In-Reply-To: <CADJx9LdGosXaWUgPyVAt4mqiRCcBZ3aN9i0t6pdoKzmXWf5=FA@mail.gmail.com> (jan's message of "Thu, 7 May 2020 19:25:04 +0100")
jan <rtm443x@googlemail.com> writes:
> I don't understand this reply as I'm very much an emacs user not an
> emacs programmer,
Sorry for that.
> but "...could query the user whether he still wants
> to enable hi-locking using font-lock, with the risk of messing up..."
> - this kind of thing, letting me know I can't have what I'm asking
> for (or can but at a risk) would be helpful so I know I'm not going to
> get it.
> I reported this as a bug out of ignorance, some hint from emacs that
> it was PEBKAC[0] would have saved me wasting Eli's time.
What I wanted to say was that your report was totally justified because
what the docstring tells about font-lock mode is a bit misleading.
Maybe hi-lock could also tell you which method of highlighting it
chooses. And maybe it would also make sense to allow using the
font-lock mode based method in modes that don't implemented font-lock,
I'm not sure.
Michael.
prev parent reply other threads:[~2020-05-07 23:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 11:32 bug#41124: 26.3; highlight regexp not working properly - not updating as you type jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.41124.B.158885115315161.ack@debbugs.gnu.org>
2020-05-07 11:39 ` bug#41124: Acknowledgement (26.3; highlight regexp not working properly - not updating as you type) jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 12:57 ` bug#41124: 26.3; highlight regexp not working properly - not updating as you type Eli Zaretskii
2020-05-07 12:55 ` Eli Zaretskii
[not found] ` <CADJx9LfmRc+CoiVmzb_sa=mgQSwTxPbjNPYPEr9ss+heeebN_g@mail.gmail.com>
2020-05-07 14:05 ` Eli Zaretskii
2020-05-07 15:36 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 16:54 ` Eli Zaretskii
2020-05-07 17:32 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 17:58 ` Eli Zaretskii
2020-05-07 17:29 ` Michael Heerdegen
2020-05-07 17:58 ` Eli Zaretskii
2020-05-07 23:12 ` Michael Heerdegen
2020-05-08 14:27 ` Eli Zaretskii
2022-03-23 12:40 ` Lars Ingebrigtsen
2020-05-07 18:25 ` jan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-07 18:42 ` Eli Zaretskii
2020-05-07 23:20 ` Michael Heerdegen [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=877dxn8h8p.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=41124@debbugs.gnu.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).