unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 30073@debbugs.gnu.org, juri@linkov.net
Subject: bug#30073: 27.0.50; dired-do-delete ignores customization for short answers
Date: Thu, 11 Jan 2018 17:52:45 +0200	[thread overview]
Message-ID: <83po6g4cky.fsf@gnu.org> (raw)
In-Reply-To: <87o9m1nlpl.fsf@gmail.com> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Thu, 11 Jan 2018 03:00:38 +0000
> Cc: 30073@debbugs.gnu.org
> 
> Juri Linkov <juri@linkov.net> writes:
> 
> > I customized ‘yes-or-no-p’ in ~/.emacs to short answers:
> >
> >   (fset 'yes-or-no-p 'y-or-n-p)
> >
> > but now ‘dired-do-delete’ ignores this customization, and always requires
> > typing a full answer “yes” with RET when deleting recursively all subdirs,
> > instead of accepting just a single letter ‘y’ as before the recent change.
> >
> > I think in this case better is to accept ‘y’ for “yes”, and ‘!’ for “all”
> > like in ‘query-replace-map’.
> 
> Just linking bug#27940, where the move away from using yes-or-no-p in
> function dired-delete-file was discussed:
> 
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27940

Indeed, this horse has been beaten to death already.  The current
solution is for you to set dired-deletion-confirmer to y-or-n-p.
Admittedly, that's not a very user-friendly customization method, but
then neither is fset.





  reply	other threads:[~2018-01-11 15:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 21:41 bug#30073: 27.0.50; dired-do-delete ignores customization for short answers Juri Linkov
2018-01-11  3:00 ` Basil L. Contovounesios
2018-01-11 15:52   ` Eli Zaretskii [this message]
2018-01-11 17:34     ` Basil L. Contovounesios
2018-01-11 18:01       ` Eli Zaretskii
2018-01-11 19:39         ` Basil L. Contovounesios
2018-01-11 21:57         ` Juri Linkov
2018-01-11 21:54     ` Juri Linkov
2018-01-12  9:57       ` Eli Zaretskii
2018-01-13 22:38         ` Juri Linkov
2018-01-14 11:01           ` Tino Calancha
2018-01-14 22:53             ` Juri Linkov
2018-01-15  5:19               ` Eli Zaretskii
2018-01-15 23:02                 ` Juri Linkov
2018-01-16 17:56                   ` Eli Zaretskii
2018-01-17 22:56                     ` Juri Linkov
2018-01-18 21:11                       ` Juri Linkov
2018-01-15 17:01               ` Drew Adams
2018-01-15 23:13                 ` Juri Linkov
2018-01-16  0:48                   ` Drew Adams
2018-01-17 22:03                     ` Juri Linkov
2018-01-18  3:36                       ` Eli Zaretskii
2018-01-18 21:12                         ` Juri Linkov
2018-01-21 21:46                           ` Juri Linkov
2018-01-25 18:04                             ` Drew Adams
2018-01-25 21:20                               ` Juri Linkov
2018-01-25 21:48                                 ` Drew Adams
2018-01-26  7:57                                 ` Eli Zaretskii
2018-01-27 21:20                                   ` Juri Linkov

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=83po6g4cky.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30073@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=juri@linkov.net \
    /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).