GNU bug report logs - #79065
31.0.50; [PATCH] Allow inverting the meaning of 'quit-window-kill-buffer'

Previous Next

Package: emacs;

Reported by: Jim Porter <jporterbugs <at> gmail.com>

Date: Mon, 21 Jul 2025 05:24:02 UTC

Severity: normal

Tags: patch

Found in version 31.0.50

Full log


Message #38 received at 79065 <at> debbugs.gnu.org (full text, mbox):

From: Jim Porter <jporterbugs <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rudalics <at> gmx.at, 79065 <at> debbugs.gnu.org, juri <at> linkov.net
Subject: Re: bug#79065: 31.0.50; [PATCH] Allow inverting the meaning of
 'quit-window-kill-buffer'
Date: Tue, 29 Jul 2025 09:35:57 -0700
On 7/29/2025 3:44 AM, Eli Zaretskii wrote:
>> From: Jim Porter <jporterbugs <at> gmail.com>
>>
>> However, another way to do this would be a tri-state:
>>
>> * no prefix: obey 'quit-window-kill-buffer'
>> * C-u: always kill
>> * C--: always bury
[snip]
> 
> That might solve the interactive case (though maybe not in a very
> convenient way), but what about calls from Lisp?

I think we could make the Lisp calls work like you suggested, where the 
KILL argument can be:

* 'nil': obey 'quit-window-kill-buffer'
* 'bury': always bury
* 'kill' (or any other non-nil value for compatibility): always kill

As for interactive use, I'm not sure whether the behavior proposed above 
would be more convenient for the average user or whether having the 
prefix arg mean "do the opposite of what it would normally do" would be 
more convenient. The behavior above is simpler to explain though, and 
when using a prefix arg, a user can always predict what will actually 
happen.




This bug report was last modified 51 days ago.

Previous Next


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