From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31782@debbugs.gnu.org, sdl.web@gmail.com
Subject: bug#31782: 26.1; dired-recursive-deletes broken
Date: Tue, 12 Jun 2018 17:55:21 -0400 [thread overview]
Message-ID: <87po0vy8ja.fsf@gmail.com> (raw)
In-Reply-To: <834li9qlu3.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Jun 2018 20:23:00 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Noam Postavsky <npostavs@gmail.com>
>> Date: Mon, 11 Jun 2018 10:33:50 -0400
>> Cc: 31782@debbugs.gnu.org
>>
>> > I am annoyed to answer this question in 26.1 constantly
>> >
>> > Recursively trash XXX? [yes, no, all, quit, help]
>> >
>> > Previously there is only yes or no (which I replace with y or n). Now I
>> > have to type all of these things.
>>
>> I think this is solved in the master branch. See Bug#30073.
>
> Should we backport that to the emacs-26 branch?
Probably yes. I have the impression that yes-or-no-p is sort of a
counterexample to what Leo mentioned in Bug#31772; that is, many (most?)
people are not very happy with it, but it's so easy to just do (fset
'yes-or-no-p #'y-or-n-p) so nobody bothers to complain about it. But
it's a "customization" that breaks down in cases like this one.
next prev parent reply other threads:[~2018-06-12 21:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 5:09 bug#31782: 26.1; dired-recursive-deletes broken Leo Liu
2018-06-11 14:33 ` Noam Postavsky
2018-06-11 17:23 ` Eli Zaretskii
2018-06-12 21:55 ` Noam Postavsky [this message]
2018-06-13 2:32 ` Eli Zaretskii
2018-06-14 4:15 ` Leo Liu
2018-06-14 13:05 ` Noam Postavsky
2018-06-14 13:26 ` Leo Liu
2018-06-15 11:24 ` Noam Postavsky
2018-07-31 1:39 ` Noam Postavsky
2018-07-31 16:00 ` Eli Zaretskii
2018-08-01 4:35 ` Richard Stallman
2018-08-01 6:04 ` Eli Zaretskii
2018-08-01 13:00 ` Basil L. Contovounesios
2018-08-04 16:02 ` Noam Postavsky
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=87po0vy8ja.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31782@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sdl.web@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.