GNU bug report logs - #77224
[PATCH] New minor mode 'cursor-indicators-mode'

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Elijah Gabe Pérez <eg642616 <at> gmail.com>
Cc: 77224 <at> debbugs.gnu.org, juri <at> linkov.net, dancol <at> dancol.org,
 mail <at> daniel-mendler.de
Subject: Re: bug#77224: [PATCH] New minor mode 'cursor-indicators-mode'
Date: Tue, 01 Apr 2025 14:42:58 +0300

> From: Elijah Gabe Pérez <eg642616 <at> gmail.com>
> Cc: 77224 <at> debbugs.gnu.org,  dancol <at> dancol.org,  mail <at> daniel-mendler.de,
>   juri <at> linkov.net
> Date: Mon, 31 Mar 2025 17:41:15 -0600
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
>  Let's please discuss your ideas before you implement them, to make
>  sure you don't work on some ideas that we might object to.
> 
> Sure.
> 
> The code needs to run each time the cursor moves, (is there
> a function/code that do this?) and each time user changes window
> (because cursor color is not buffer-local).

I understand the general idea, but did you have more detailed ideas
for how to implement that?

And I'm not sure I understand why cursor movement needs this to run,
since the cursor appearance doesn't depend on its position, it depends
on state of overwrite-mode, buffer-read-only, and other similar state
variables, which don't change with buffer or cursor position.  So what
am I missing?

> I think that using variable watchers would be better and keep
> this defcustom (it will only use variables):
> 
> 
> (defcustom cursor-indicators
>   '((overwrite-mode . "red")
>     (buffer-read-only "green" hollow)
>     (current-input-method . "blue"))
>     [...]

If each state has a variable you can watch, then yes.

Previous Next

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