Re: Setting 'which-key-dont-use-unicode'

["Kévin Le Gouguec" <kevin.legouguec@gmail.com>]

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Mon, 24 Jun 2024 07:12:27 +0000, Philip Kaludercic <philipk@posteo.net> said:
>     >> And FWIW there does seem to be precedent for that approach:
>     >> e.g. ls-lisp-emulation's setter calls ls-lisp-set-options, which resets
>     >> all variables tagged :set-after '(ls-lisp-emulation)… except
>     >> ls-lisp-use-string-collate; wondering if that's intentional 🤔
>
>     Philip> I think that was a mistake. `ls-lisp-emulation' was added in 2010, where
>     Philip> all the options it reeevaluates already existed, and
>     Philip> `ls-lisp-use-string-collate' was added in 2014, and it was forgotten to
>     Philip> update `ls-lisp-set-options' as well.
>
> Fixed in emacs-30. (this is what happens when my simulations take a
> long time to start 😀).

Thank you both 🙇

Philip Kaludercic <philipk@posteo.net> writes:

>> (And now wondering if :set-after '(SYMS…) should make this pattern
>> easier by storing the reverse dependency, e.g. in a new
>> 'custom-dependents property attached to each symbol in SYMS…  Could that
>> make these setters easier to maintain?)
>>
>> Anyhoo; straying far from the original report.  Thanks again for
>> confirming & proposing a fix!
>
> I have a few ideas on this topic, and we can gladly discuss it in a bug
> report.

ACK; let me know if you'd like me to file that report - as a general
enhancement request for :set-after, IIUC?