GNU bug report logs - #71140
30.0.50; winner-dont-bind-my-keys not respected

Previous Next

Full log

Message #16 received at 71140-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Johann Höchtl <johann.hoechtl <at> gmail.com>,
 71140-done <at> debbugs.gnu.org
Subject: Re: bug#71140: 30.0.50; winner-dont-bind-my-keys not respected
Date: Fri, 28 Feb 2025 18:19:43 -0800

Eli Zaretskii <eliz <at> gnu.org> writes:

> [Please use Reply All to reply, to keep the bug address on the CC list.
>
>> From: Johann Höchtl <johann.hoechtl <at> gmail.com>
>> Date: Thu, 23 May 2024 17:55:22 +0200
>>
>> Am Do., 23. Mai 2024 um 15:05 Uhr schrieb Eli Zaretskii <eliz <at> gnu.org>:
>>
>>  > From: Johann Höchtl <johann.hoechtl <at> gmail.com>
>>  > Date: Thu, 23 May 2024 08:15:26 +0200
>>  >
>>  > I customized winner-dont-bind-my-keys 't but C-<left> or C-<right> are
>>  > still bound to winner-mode, in my case overriding indentation shift
>>  > commands of markdown-mode.
>>  >
>>  > As it seems, the customization variable is not respected.
>>
>>  I cannot reproduce this.  Please tell in more detail how you
>>  customized the variable, maybe that's where the problem lies.
>>
>> I simply called M-x customize-group  winner, therein set winner-mode boolean to 't and Winner Dont Bind My
>> Keys to on, this results in
>>
>> (custom-set-variables
>>  '(winner-dont-bind-my-keys t)
>>  '(winner-mode t)
>> )
>
> I think after you customize this, you need to turn the mode off and on
> again.
>
> Or customize the variable with setq instead.

Yes, indeed.  AFAIU, that's the expected interface.

I think we'd take patches to improve the situation, but for now, I'm
closing this bug.  Thanks.

Previous Next

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