From: Glenn Morris <rgm@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 36110@debbugs.gnu.org
Subject: bug#36110: find-dired not sorted on any field nor provides a way
Date: Thu, 13 Jun 2019 19:40:11 -0400 [thread overview]
Message-ID: <p3blz16omc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r27xglua.fsf@mail.linkov.net> (Juri Linkov's message of "Fri, 14 Jun 2019 00:30:05 +0300")
Juri Linkov wrote:
>>>> Long ago I customized find-ls-option to this value
>>>>
>>>> (setq find-ls-option '("-exec ls -ld {} \\;" . "-ld"))
But that has nothing to do with sorting?
find -exec ls -ld {} ";"
will give unsorted output, as always.
> -and the second telling Dired to parse the output.
> +and the second telling Dired to parse the output. To sort file names
> +lexicographically, you can customize @code{find-ls-option} to the value
> +@code{'("-exec ls -ld @{@} +" . "-ld")}
Oh, I see you've changed it to the "+" form.
It looks like this does give sorted output, but I find it surprising.
Is it assured?
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.
next prev parent reply other threads:[~2019-06-13 23:40 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 [this message]
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
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=p3blz16omc.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=36110@debbugs.gnu.org \
--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 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.