GNU bug report logs - #38039
27.0.50; Dired kill associated buffers matching extension

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38039 in the body.
You can then email your comments to 38039 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: Jeff Spencer <jeffspencerd <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0.50; Dired kill associated buffers matching extension
Date: Sat, 2 Nov 2019 20:22:44 -0400

[Message part 1 (text/plain, inline)]

I submited the prior bug request Dired dired-clean-up-after-deletion
bug.

A feature enhancement that is related to this is that I would like to be
able to set
the file extensions that would automatically be deleted. Then for the
other file extensions confirm before deleting the buffers. I see
possiblyl changing dired-clean-confirm-killing-deleted-buffers to
allowing three differnt options. One is nil meaning don't ask and
automatically kill everything. One is t meaning confirm all buffers. The
last is a list like '(.txt .pdf)) that will allow these extensions to
automatically be killed but all others it will ask. But the problem with
this is the dired and sub-directory killing part. If you specify a list,
I think there needs a seperate variable that you can control the dired
buffer killing from the regular buffer killing.

[Message part 2 (text/html, inline)]

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

From: Jeff Spencer <jeffspencerd <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: 27.0.50; Dired kill associated buffers matching extension
Date: Sat, 2 Nov 2019 20:30:17 -0400

[Message part 1 (text/plain, inline)]

Sorry, the bug report I submitted was bug #38037.

On Sat, Nov 2, 2019 at 8:22 PM Jeff Spencer <jeffspencerd <at> gmail.com> wrote:

>
> I submited the prior bug request Dired dired-clean-up-after-deletion
> bug.
>
> A feature enhancement that is related to this is that I would like to be
> able to set
> the file extensions that would automatically be deleted. Then for the
> other file extensions confirm before deleting the buffers. I see
> possiblyl changing dired-clean-confirm-killing-deleted-buffers to
> allowing three differnt options. One is nil meaning don't ask and
> automatically kill everything. One is t meaning confirm all buffers. The
> last is a list like '(.txt .pdf)) that will allow these extensions to
> automatically be killed but all others it will ask. But the problem with
> this is the dired and sub-directory killing part. If you specify a list,
> I think there needs a seperate variable that you can control the dired
> buffer killing from the regular buffer killing.
>

[Message part 2 (text/html, inline)]

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Jeff Spencer <jeffspencerd <at> gmail.com>
Cc: 38039 <at> debbugs.gnu.org
Subject: Re: bug#38039: 27.0.50; Dired kill associated buffers matching
 extension
Date: Sun, 08 May 2022 16:06:38 +0200

Jeff Spencer <jeffspencerd <at> gmail.com> writes:

> A feature enhancement that is related to this is that I would like to be able to set
> the file extensions that would automatically be deleted. Then for the
> other file extensions confirm before deleting the buffers. I see
> possiblyl changing dired-clean-confirm-killing-deleted-buffers to
> allowing three differnt options. One is nil meaning don't ask and
> automatically kill everything. One is t meaning confirm all buffers. The
> last is a list like '(.txt .pdf)) that will allow these extensions to
> automatically be killed but all others it will ask. But the problem with
> this is the dired and sub-directory killing part. If you specify a list,
> I think there needs a seperate variable that you can control the dired
> buffer killing from the regular buffer killing. 

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

In my opinion, this would require so much customisation that I don't
think it's a feature that many people would use.  So I'm closing this as
a "wontfix".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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