From: Philip Kaludercic <philipk@posteo.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: master fa4203300fd: Merge remote-tracking branch 'origin/feature/which-key-in-core'
Date: Mon, 24 Jun 2024 20:23:32 +0000 [thread overview]
Message-ID: <87frt22ipn.fsf@posteo.net> (raw)
In-Reply-To: <87sex2qh25.fsf@gmx.de> (Michael Albinus's message of "Mon, 24 Jun 2024 21:25:22 +0200")
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Michael Albinus <michael.albinus@gmx.de> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> branch: master
>> commit fa4203300fde6820a017bf1089652fb95759d68c
>> Merge: a7dff8c53dd cc0a3a5f65b
>> Author: Philip Kaludercic <philipk@posteo.net>
>> Commit: Philip Kaludercic <philipk@posteo.net>
>>
>> Merge remote-tracking branch 'origin/feature/which-key-in-core'
>> ---
>> etc/NEWS | 7 +
>> lisp/which-key.el | 2814 ++++++++++++++++++++++++++++++++++++++++++
>> test/lisp/which-key-tests.el | 267 ++++
>> 3 files changed, 3088 insertions(+)
>
> Seen in the emacs-30 branch:
>
> # make -C test test-custom-opts
> ...
> The following options might have problems:
> variable: which-key-separator
> value: nil
> type: (string)
> variable: which-key-ellipsis
> value: nil
> type: (string)
> ...
> FAILED 1/1 check-for-wrong-custom-opts (39.873179 sec) at misc/test-custom-opts.el:33
>
> Ran 1 tests, 0 results as expected, 1 unexpected (2024-06-24 21:14:57+0200, 40.332174 sec)
>
> 1 unexpected results:
> FAILED check-for-wrong-custom-opts
This should fix the issue:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-lisp-which-key.el-which-key-dont-use-unicode-Add-ini.patch --]
[-- Type: text/x-patch, Size: 1131 bytes --]
From c707ba33a4c3b1de7cb7e8c35736e48ced81a0e0 Mon Sep 17 00:00:00 2001
From: Philip Kaludercic <philipk@posteo.net>
Date: Mon, 24 Jun 2024 22:15:25 +0200
Subject: [PATCH] ; * lisp/which-key.el (which-key-dont-use-unicode): Add
:initialize
This fixes the change from 768e92b9, which accidentally would call
'custom-reevaluate-setting' on user options before they were registered,
initialising their default value to nil. When the 'defcustom'
expressions were evaluated later on, they were not properly initialised
as their variables were already bound to some value (nil).
https://lists.gnu.org/archive/html/emacs-devel/2024-06/msg00825.html
---
lisp/which-key.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/which-key.el b/lisp/which-key.el
index 91007ce4ada..8b78bfb2576 100644
--- a/lisp/which-key.el
+++ b/lisp/which-key.el
@@ -133,6 +133,7 @@ which-key-dont-use-unicode
(mapc #'custom-reevaluate-setting
'(which-key-separator
which-key-ellipsis)))
+ :initialize #'custom-initialize-changed
:type 'boolean
:package-version "1.0" :version "30.1")
--
2.45.2
[-- Attachment #3: Type: text/plain, Size: 37 bytes --]
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-06-24 20:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171873998859.23986.6867742580209068033@vcs2.savannah.gnu.org>
[not found] ` <20240618194635.AC606C1FB66@vcs2.savannah.gnu.org>
2024-06-19 7:20 ` master fa4203300fd: Merge remote-tracking branch 'origin/feature/which-key-in-core' Robert Pluim
2024-06-19 7:42 ` Philip Kaludercic
2024-06-19 8:49 ` Robert Pluim
2024-06-19 12:01 ` Robert Pluim
2024-06-19 12:33 ` Stefan Kangas
2024-06-19 12:47 ` Robert Pluim
2024-06-19 13:00 ` Philip Kaludercic
2024-06-19 13:10 ` Eli Zaretskii
2024-06-19 13:32 ` Robert Pluim
2024-06-19 13:37 ` tomas
2024-06-19 13:43 ` Robert Pluim
2024-06-19 13:55 ` tomas
2024-06-19 14:41 ` Eli Zaretskii
2024-06-20 4:21 ` tomas
2024-06-19 11:57 ` Eli Zaretskii
2024-06-19 12:08 ` Robert Pluim
2024-06-24 19:25 ` Michael Albinus
2024-06-24 20:23 ` Philip Kaludercic [this message]
2024-06-25 6:37 ` Michael Albinus
2024-06-25 9:26 ` Philip Kaludercic
2024-06-25 10:04 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frt22ipn.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.