From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rtm443x@googlemail.com, 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:12:20 +0200 [thread overview]
Message-ID: <87blmz8hm3.fsf@web.de> (raw)
In-Reply-To: <83eervk4ob.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 07 May 2020 20:58:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> > @Eli: the docstring of `hi-lock-mode' just says:
> >
> > "In buffers where Font Lock mode is enabled, patterns are
> > highlighted using font lock."
> >
> > That's wrong, I think the docstring should be adapted.
>
> Please suggest how to say that better.
"is implemented and enabled" maybe? We could also say that Font Lock
mode must be enabled and the MODE must fulfill `font-lock-specified-p'.
Or a combination of those words.
Michael.
next prev parent reply other threads:[~2020-05-07 23:12 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 [this message]
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
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=87blmz8hm3.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=41124@debbugs.gnu.org \
--cc=eliz@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).