all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 27940@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#27940: Recursively delete dir34? (yes, no, all, quit)
Date: Fri, 04 Aug 2017 11:31:51 +0300	[thread overview]
Message-ID: <83a83fybrc.fsf@gnu.org> (raw)
In-Reply-To: <87r2wrkacy.fsf@calancha-pc> (message from Tino Calancha on Fri,  04 Aug 2017 17:25:49 +0900)

> From: Tino Calancha <tino.calancha@gmail.com>
> Cc: 27940@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Fri, 04 Aug 2017 17:25:49 +0900
> 
> > dired-do-flagged-delete and me interaction:
> > Recursively delete dcepc? (yes or no) yes
> > Recursively delete emmpc? (yes or no) yes
> > Recursively delete zpspc? (yes or no) yes
> > Recursively delete dgcpc? (yes or no) yes
> >
> > Wouldn't it be nice if there was instead:
> > Recursively delete dgcpc? (yes, no, all, quit)
> >
> > Yes, if before we started we set the variables we needn't be asked all
> > those questions.
> >
> > But now *midway* through the list, we decide we would like no more
> > question, there should be a way, without needing to quit and start over,
> > even if doing that isn't so bad.
> Thanks for the suggestion.
> You can already quit with '\C-g'.
> Concerning accept 'all' in the prompt, i am not sure:
> it's a bit dangerous operation.
> 
> In the other hand:
> 1) Customize `dired-recursive-deletes' to value 'always.
> 2) Do the deletion.
> 3) Set back `dired-recursive-deletes' to its original value.

Actually, I think the value he wants is 'top'.

I don't object to accepting something like "!" to mean "all", I
believe we already have a few features that do this, and the
implementation should be simple, I think.  (Creeping featurism, I
know, but what else did you expect from users who have no real bugs to
report? ;-)

> How about if `dired-do-delete' called interactively with 2 prefices
> performs recursive deletions?
> Eli?

Sounds too cumbersome to me.





  reply	other threads:[~2017-08-04  8:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 23:26 bug#27940: Recursively delete dir34? (yes, no, all, quit) 積丹尼 Dan Jacobson
2017-08-04  8:25 ` Tino Calancha
2017-08-04  8:31   ` Eli Zaretskii [this message]
2017-08-04  9:29     ` Tino Calancha
2017-08-04  9:37       ` Tino Calancha
2017-08-04 12:46       ` Eli Zaretskii
2017-08-04 14:33         ` Tino Calancha
2017-08-04 14:54           ` Eli Zaretskii
2017-08-06  4:52             ` Tino Calancha
     [not found]               ` <87k22e9obk.fsf@ctlt579.codethink.co.uk>
2017-08-09  5:54                 ` Tino Calancha
2017-10-15 14:17                   ` Noam Postavsky
2017-10-16  5:20                     ` Tino Calancha
2017-10-16 10:36                       ` Noam Postavsky
2017-10-16 10:43                         ` Tino Calancha
2017-10-17 12:40                           ` Noam Postavsky
     [not found]         ` <<871sorz9kg.fsf@calancha-pc>
     [not found]           ` <<83tw1nwfhp.fsf@gnu.org>
2017-08-04 15:51             ` Drew Adams
2017-08-04 16:18               ` Tino Calancha
2017-08-04 16:22                 ` Drew Adams
2017-08-04 16:34                   ` Tino Calancha
     [not found] <<87o9rwxmfz.fsf@jidanni.org>

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83a83fybrc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27940@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=tino.calancha@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.