From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jeff Spencer <jeffspencerd@gmail.com>
Cc: 38039@debbugs.gnu.org
Subject: bug#38039: 27.0.50; Dired kill associated buffers matching extension
Date: Sun, 08 May 2022 16:06:38 +0200 [thread overview]
Message-ID: <87mtfsdspd.fsf@gnus.org> (raw)
In-Reply-To: <CALmFPZ17Jb8o1-7pNH7EbraHFM9cFocmH7rPa0i61=wrC0_0og@mail.gmail.com> (Jeff Spencer's message of "Sat, 2 Nov 2019 20:22:44 -0400")
Jeff Spencer <jeffspencerd@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
prev parent reply other threads:[~2022-05-08 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 0:22 bug#38039: 27.0.50; Dired kill associated buffers matching extension Jeff Spencer
2019-11-03 0:30 ` Jeff Spencer
2022-05-08 14:06 ` Lars Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtfsdspd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=38039@debbugs.gnu.org \
--cc=jeffspencerd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).