GNU bug report logs -
#39597
27.0.60: M-x occur adds fontification to fundamental-mode
Previous Next
Reported by: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Date: Fri, 14 Feb 2020 08:19:02 UTC
Severity: normal
Tags: fixed
Found in version 27.0.60
Fixed in version 28.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Eli Zaretskii <eliz <at> gnu.org> writes:
> The fix installed on master
(If you are referring to Stefan's patch, AFAICT it has not been
committed to master yet.)
> is in a much more general place, and will
> affect much more than just occur-engine. I'm okay with a bug-fix
> change on the release branch which is local to this place in
> replace.el, but I don't want to risk breaking unrelated code by
> changing font-lock.el.
Idle musing: I wonder if something could be done inside
fundamental-mode. It's not the only fontification issue I've noticed
there[1].
> Another alternative is to revert the offending changes in fb16313025
> on the release branch. Since it is an enhancement, perhaps we could
> live without it in Emacs 27.
I don't have a preference about that. Juri?
[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…
This bug report was last modified 5 years and 144 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.