[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: kill-matching-buffers without confirmation

From: Kaushal Modi
Subject: Re: kill-matching-buffers without confirmation
Date: Mon, 22 May 2017 19:00:37 +0000

On Mon, May 22, 2017 at 2:45 PM Clément Pit-Claudel <address@hidden> wrote:
Or a defcustom, since it seems that the usual approach is to override the behavior unconditionally.

A defcustom seems too risky for this. A user can unknowingly copy that var from somewhere and then end up killing modified buffers without confirmation.

Add a new defun that just sets the new optional arg to non-nil value is less risky as the user would then be knowingly calling the risky variant. The default kill-matching-buffers will still remain safe.

What do you think? 

Kaushal Modi

reply via email to

[Prev in Thread] Current Thread [Next in Thread]