Re: emacs-30 768e92b9c02: Update options that depend on 'which-key-dont-use-unicode'

[Philip Kaludercic <philipk@posteo.net>]

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Mon, 24 Jun 2024 18:49:43 +0000, Philip Kaludercic <philipk@posteo.net> said:
>     >> That works for me, although I wonʼt claim to understand why 😀
>
>     Philip> My reasoning is that this will only run the setter if the value is
>     Philip> /changed/, right?  So if we set `which-key-dont-use-unicode' is set
>     Philip> before we load which-key, then the user option inherits the
>     Philip> configuration and the other two options use the current value to
>     Philip> determine their default value.  If on the other hand we change the user
>     Philip> option after which-key has been loaded, then the custom setter will take
>     Philip> effect, and will re-load the default value, which has previously been
>     Philip> set to the (if ...) expression, as was the case before.
>
> I spoke too soon, or my testing was wrong, Iʼm still getting
> `which-key-separator' as nil when I customize
> `which-key-dont-use-unicode' to nil in emacs-30.
>
> Do you want a M-x report-emacs-bug?

I think that would make sense.

> Robert

-- 
	Philip Kaludercic on peregrine