From: Noam Postavsky <npostavs@gmail.com>
To: Leo Liu <sdl.web@gmail.com>
Cc: 31782@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#31782: 26.1; dired-recursive-deletes broken
Date: Fri, 15 Jun 2018 07:24:53 -0400 [thread overview]
Message-ID: <87wov0uwai.fsf@gmail.com> (raw)
In-Reply-To: <m1in6lebxb.fsf@gmail.com> (Leo Liu's message of "Thu, 14 Jun 2018 21:26:56 +0800")
Leo Liu <sdl.web@gmail.com> writes:
> On 2018-06-14 09:05 -0400, Noam Postavsky wrote:
>>> (setq dired-recursive-deletes 'aways) still get
>
> I got an unfortunate typo here.
Oh, hah, I missed that too.
So, looking at the Bug#30073 fix, the new (currently being introduced in
Emacs 27) read-answer function looks pretty similar to
read-multiple-choice. Perhaps some sharing is in order?
Another thing is that the defcustom default value trick doesn't work as
intended (as far as I understand the intention, at least).
;; For backward compatibility check if short y/n answers are preferred.
(defcustom read-answer-short (eq (symbol-function 'yes-or-no-p) 'y-or-n-p)
"If non-nil, accept short answers to the question."
For a user with .emacs consisting of
(fset 'yes-or-no-p 'y-or-n-p)
<f1> v read-answer-short RET gives:
read-answer-short is a variable defined in ‘map-ynp.el’.
Its value is nil
Original value was t
I think we'd want some `auto' setting which would tell read-answer to
look at the yes-or-no-p function value at run time.
next prev parent reply other threads:[~2018-06-15 11:24 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
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 [this message]
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=87wov0uwai.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31782@debbugs.gnu.org \
--cc=juri@linkov.net \
--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.