From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36110@debbugs.gnu.org
Subject: bug#36110: find-dired not sorted on any field nor provides a way
Date: Fri, 14 Jun 2019 22:12:07 +0300 [thread overview]
Message-ID: <87sgscyoag.fsf@mail.linkov.net> (raw)
In-Reply-To: <83sgscy9iq.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Jun 2019 09:18:53 +0300")
>> Anyway, this issue has been very recently fixed in bug#29513
>> (of which this is a duplicate) via find-dired-refine-function.
>> So I suggest not documenting the above.
>
> We could document both ways.
>
> Btw, the commit which fixed bug#29513 didn't call out the change in
> NEWS, let alone in the manual, so we should definitely improve the
> docs regarding this issue anyway.
Also I see no way to disable its default value with something like:
diff --git a/lisp/find-dired.el b/lisp/find-dired.el
index 2c76179da0..c563ae533a 100644
--- a/lisp/find-dired.el
+++ b/lisp/find-dired.el
@@ -123,7 +138,10 @@ find-dired-refine-function
output of `find' (one file per line) when this function is called."
:version "27.1"
:group 'find-dired
- :type 'function)
+ :type '(choice (const :tag "Sort file names lexicographically"
+ find-dired-sort-by-filename)
+ (function :tag "Refining function")
+ (const :tag "No refining" nil)))
(defvar find-args nil
"Last arguments given to `find' by \\[find-dired].")
next prev parent reply other threads:[~2019-06-14 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 23:27 bug#36110: find-dired not sorted on any field nor provides a way 積丹尼 Dan Jacobson
2019-06-06 20:28 ` Juri Linkov
2019-06-06 21:21 ` Drew Adams
2019-06-07 0:25 ` 積丹尼 Dan Jacobson
2019-06-13 21:30 ` Juri Linkov
2019-06-13 23:40 ` Glenn Morris
2019-06-14 0:12 ` Glenn Morris
2019-06-14 6:26 ` Andreas Schwab
2019-06-14 19:09 ` Juri Linkov
2019-06-14 19:10 ` Juri Linkov
2019-06-14 6:18 ` Eli Zaretskii
2019-06-14 19:12 ` Juri Linkov [this message]
2019-06-14 6:06 ` Eli Zaretskii
2019-06-15 22:36 ` Juri Linkov
2019-06-16 2:39 ` Eli Zaretskii
2019-06-16 8:37 ` Andreas Schwab
2019-06-16 14:02 ` Eli Zaretskii
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=87sgscyoag.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=36110@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.