[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31782: 26.1; dired-recursive-deletes broken
From: |
Noam Postavsky |
Subject: |
bug#31782: 26.1; dired-recursive-deletes broken |
Date: |
Fri, 15 Jun 2018 07:24:53 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
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.
- bug#31782: 26.1; dired-recursive-deletes broken, Leo Liu, 2018/06/11
- bug#31782: 26.1; dired-recursive-deletes broken, Noam Postavsky, 2018/06/11
- bug#31782: 26.1; dired-recursive-deletes broken, Eli Zaretskii, 2018/06/11
- bug#31782: 26.1; dired-recursive-deletes broken, Noam Postavsky, 2018/06/12
- bug#31782: 26.1; dired-recursive-deletes broken, Eli Zaretskii, 2018/06/12
- bug#31782: 26.1; dired-recursive-deletes broken, Leo Liu, 2018/06/14
- bug#31782: 26.1; dired-recursive-deletes broken, Noam Postavsky, 2018/06/14
- bug#31782: 26.1; dired-recursive-deletes broken, Leo Liu, 2018/06/14
- bug#31782: 26.1; dired-recursive-deletes broken,
Noam Postavsky <=