From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 39597@debbugs.gnu.org
Subject: bug#39597: 27.0.60: M-x occur adds fontification to fundamental-mode
Date: Tue, 25 Feb 2020 21:45:29 +0100 [thread overview]
Message-ID: <87imjue6qe.fsf@gmail.com> (raw)
In-Reply-To: <871rqmnob4.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 23 Feb 2020 02:24:15 +0200")
Juri Linkov <juri@linkov.net> writes:
>> [1] E.g. (I was about to report this as a distinct issue… someday…)
>>
>> C-x b foo
>> foo RET bar RET baz RET
>> M-s h r a RET RET
>> aaaa
>>
>> ⇒ In all modes *but* fundamental-mode, hi-lock-mode dynamically
>> highlights new matches (e.g. the added "aaaa" string here).
>>
>> This bug is not strictly related to the current one, since the
>> former has been with us since at least 26.3, but that does make me
>> wonder whether both issues could be solved by turning some font-lock
>> knob in fundamental-mode…
>
> Searching for "font-lock-specified-p" in hi-lock.el
> shows these fragments of code. This first condition decides
> whether to use font-lock for highlighting matches
> that returns nil in fundamental-mode:
>
> (if (and font-lock-mode (font-lock-specified-p major-mode))
>
> ;; FIXME: Calling `font-lock-remove-keywords' causes
> ;; `font-lock-specified-p' to go from nil to non-nil (because it
> ;; calls font-lock-set-defaults). This is yet-another bug in
> ;; font-lock-add/remove-keywords, which we circumvent here by
> ;; testing `font-lock-fontified' (bug#19796).
Thanks, I'll look into this SomeDay™ before I submit a bug report then.
And thank you for fixing the other bug on emacs-27 and master!
next prev parent reply other threads:[~2020-02-25 20:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 8:18 bug#39597: 27.0.60: M-x occur adds fontification to fundamental-mode Kévin Le Gouguec
2020-02-18 0:12 ` Juri Linkov
2020-02-18 13:51 ` Stefan Monnier
2020-02-18 22:49 ` Juri Linkov
2020-02-20 14:54 ` Eli Zaretskii
2020-02-20 19:10 ` Kévin Le Gouguec
2020-02-20 19:58 ` Eli Zaretskii
2020-02-20 22:27 ` Kévin Le Gouguec
2020-02-21 7:40 ` Eli Zaretskii
2020-02-21 19:09 ` Kévin Le Gouguec
2020-02-23 0:24 ` Juri Linkov
2020-02-25 20:45 ` Kévin Le Gouguec [this message]
2020-02-23 0:37 ` Juri Linkov
2020-02-21 0:04 ` Juri Linkov
2020-02-19 18:57 ` Kévin Le Gouguec
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=87imjue6qe.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=39597@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).