emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#28373: closed ([PATCH] New variable controls wheth


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#28373: closed ([PATCH] New variable controls whether dired confirms to kill buffers visiting deleted files)
Date: Fri, 08 Sep 2017 09:42:01 +0000

Your message dated Fri, 08 Sep 2017 12:41:04 +0300
with message-id <address@hidden>
and subject line Re: bug#28373: [PATCH] New variable controls whether dired 
confirms to kill buffers visiting deleted files
has caused the debbugs.gnu.org bug report #28373,
regarding [PATCH] New variable controls whether dired confirms to kill buffers 
visiting deleted files
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
28373: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28373
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH] New variable controls whether dired confirms to kill buffers visiting deleted files Date: Wed, 06 Sep 2017 10:42:37 -0500 User-agent: mu4e 0.9.18; emacs 25.2.1
Hello,

This is a patch to include a new variable that, when set to nil, makes dired 
kill buffers visiting deleted files without confirmation.

There are apparently some people interested in this:

https://emacs.stackexchange.com/questions/30676/how-to-always-kill-dired-buffer-when-deleting-a-folder

I read through the CONTRIBUTE file, but please let me know if something is 
wrong with the commit message and I can redo it.

Alex

Attachment: 0001-Add-dired-confirm-killing-deleted-buffers.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#28373: [PATCH] New variable controls whether dired confirms to kill buffers visiting deleted files Date: Fri, 08 Sep 2017 12:41:04 +0300
> From: Alex Branham <address@hidden>
> Cc: address@hidden
> Date: Wed, 06 Sep 2017 13:11:45 -0500
> 
> Thanks for the review. I think I've addressed the things you've brought up; 
> specific replies below.

Thanks, pushed to the master branch.

Two minor nits for the future:

 . please always mention the bug number in the commit log message
 . the NEWS entry should be marked with "+++" only if the new feature
   is described in the appropriate manual; otherwise it should be
   either marked with "---" (if it doesn't need to be in the manual),
   or not marked at all (which is a signal for the maintainers to
   consider documenting it at some future point).  This is explained
   at the beginning of NEWS.


--- End Message ---

reply via email to

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