GNU bug report logs - #6310
hi-lock-set-pattern, font-lock-mode, overlays and occur

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6310 in the body.
You can then email your comments to 6310 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Emacs Bugs <bug-gnu-emacs <at> gnu.org>
Subject: hi-lock-set-pattern, font-lock-mode, overlays and occur
Date: Sun, 30 May 2010 03:21:14 +0200

I will never understand font-lock-add-keywords, but here are some
thoughts about it and hi-lock-set-pattern.

hi-lock-set-pattern can operate with and without font lock. In the
latter case it uses overlays.

However it locks to me like it mixes those two ways a bit:

- It calls font-lock-add-keywords even when it is going to use overlays.

- Secondly it checks font-lock-fontified instead of font-lock-mode to
see whether to use overlays or not.

And it does not seem to know about jit-lock:

- It calls font-lock-fontify-buffer instead of jit-lock-refontify.


This mean that it can't work in ocurr buffers.

Beside that font-lock-mode is t in occur buffers. Is font lock used there, or?

Message #10 received at 6310 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 6310 <at> debbugs.gnu.org
Subject: Re: bug#6310: hi-lock-set-pattern, font-lock-mode, overlays and occur
Date: Thu, 03 Jun 2021 10:51:26 +0200

Lennart Borgman <lennart.borgman <at> gmail.com> writes:

> hi-lock-set-pattern can operate with and without font lock. In the
> latter case it uses overlays.
>
> However it locks to me like it mixes those two ways a bit:
>
> - It calls font-lock-add-keywords even when it is going to use overlays.
>
> - Secondly it checks font-lock-fontified instead of font-lock-mode to
> see whether to use overlays or not.
>
> And it does not seem to know about jit-lock:
>
> - It calls font-lock-fontify-buffer instead of jit-lock-refontify.
>
> This mean that it can't work in ocurr buffers.
>
> Beside that font-lock-mode is t in occur buffers. Is font lock used there, or?

(I'm going through old bug reports that unfortunately got no response at
the time.)

This bug report doesn't have a clear recipe, but I tried using
(hi-lock-set-pattern "This" 'highlight) in an *Occur* buffer, and it
seems to work fine.

So has this problem gone away in the years since it was reported, or are
you still seeing issues?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #15 received at 6310 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 6310 <at> debbugs.gnu.org
Subject: Re: bug#6310: hi-lock-set-pattern, font-lock-mode, overlays and occur
Date: Fri, 02 Jul 2021 13:18:39 +0200

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> This bug report doesn't have a clear recipe, but I tried using
> (hi-lock-set-pattern "This" 'highlight) in an *Occur* buffer, and it
> seems to work fine.
>
> So has this problem gone away in the years since it was reported, or are
> you still seeing issues?

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.