GNU bug report logs - #76687
global-hi-lock-mode prompts on its own help

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: dancol <at> dancol.org, shipmints <at> gmail.com, 76687 <at> debbugs.gnu.org
Subject: Re: bug#76687: global-hi-lock-mode prompts on its own help
Date: Mon, 03 Mar 2025 16:28:39 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Mon, 3 Mar 2025 13:39:38 +0000
> Cc: dancol <at> dancol.org, 76687 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: Ship Mints <shipmints <at> gmail.com>
> >> Date: Sun, 2 Mar 2025 13:56:37 -0500
> >> Cc: Stefan Kangas <stefankangas <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>, 76687 <at> debbugs.gnu.org
> >>
> >> Perhaps as simple as adding help modes to hi-lock-exclude-modes?  It looks like hi-lock mode exclusion
> >> logic might need a little improvement to honor derived modes.
> >
> > Any reason why Help mode should be exempt from global-hi-lock-mode?
> > This bug report shows a single instance of that mode which perhaps
> > needs to be fixed, so why disable the mode for all of the Help
> > buffers?
> 
> First, isn't the bug here that you get a prompt despite there being no
> Hi-lock lines?  Why would you prompt in that case?

I understood that there _are_ Hi-lock lines in that buffer.

> Second, and orthogonally, perhaps special-mode should be in
> hi-lock-exclude modes by default.

Again, I find no reasons to exclude special-mode.  People may wish to
highlight a regexp everywhere.

Previous Next

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