From: Robert Pluim <rpluim@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Justin Burkett" <justin@burkett.cc>,
help-gnu-emacs@gnu.org
Subject: Re: Setting 'which-key-dont-use-unicode'
Date: Mon, 24 Jun 2024 15:02:43 +0200 [thread overview]
Message-ID: <87ed8mbij0.fsf@gmail.com> (raw)
In-Reply-To: <87frt2ddb8.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 24 Jun 2024 07:12:27 +0000")
>>>>> 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 😀).
Robert
--
next prev parent reply other threads:[~2024-06-24 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 21:05 Setting 'which-key-dont-use-unicode' Kévin Le Gouguec
2024-06-24 1:44 ` Justin Burkett
2024-06-24 2:58 ` Philip Kaludercic
2024-06-24 6:06 ` Kévin Le Gouguec
2024-06-24 7:12 ` Philip Kaludercic
2024-06-24 13:02 ` Robert Pluim [this message]
2024-06-25 5:52 ` Kévin Le Gouguec
2024-06-26 13:38 ` Philip Kaludercic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed8mbij0.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=justin@burkett.cc \
--cc=kevin.legouguec@gmail.com \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).