From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 64656@debbugs.gnu.org, drew.adams@oracle.com
Subject: bug#64656: 29.0.91; Doc of minibuffer histories and completing-read - automatic addition of completions to DEFAULT list
Date: Thu, 09 Nov 2023 21:31:43 +0200 [thread overview]
Message-ID: <838r76zpsw.fsf@gnu.org> (raw)
In-Reply-To: <86jzqqj1u2.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 09 Nov 2023 19:03:49 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: drew.adams@oracle.com, 64656@debbugs.gnu.org
> Date: Thu, 09 Nov 2023 19:03:49 +0200
>
> >> I guess not many users customize 'completions-sort' to nil.
> >> Otherwise someone may notice that the order of unsorted files
> >> is reversed from the output of `ls -U`. This could be fixed by:
> >
> > The order is not reverse here, AFAICT, so please show a reproducible
> > recipe to make sure we are on the same page regarding this change.
>
> A recipe is to customize `completions-sort' to nil ("No sorting"),
> then first call `M-& ls -U RET' and afterwards `C-x C-f TAB TAB'
> and compare the contents of two buffers *Async Shell Command*
> and *Completions*. The order of files is reversed.
OK, I see it now, thanks.
But IMO this raises several issues:
. completions-sort affects all completions, not just completions of
file names, right? So why the change only for file names?
. who said that the order we get file names from readdir is the
"unsorted order", and not its reverse?
. in any case, I think we should reverse only when completions-sort
is nil, because otherwise we could adversely affect the sorting
performed on the results
next prev parent reply other threads:[~2023-11-09 19:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 23:35 bug#64656: 29.0.91; Doc of minibuffer histories and completing-read - automatic addition of completions to DEFAULT list Drew Adams
2023-07-16 5:24 ` Eli Zaretskii
2023-07-16 14:34 ` Drew Adams
2023-07-16 14:58 ` Eli Zaretskii
2023-07-18 20:27 ` Drew Adams
2023-07-19 6:35 ` Juri Linkov
2023-07-19 17:23 ` Drew Adams
2023-10-20 6:47 ` Juri Linkov
2023-10-20 16:48 ` Drew Adams
2023-10-29 18:29 ` Juri Linkov
2023-10-29 22:15 ` Drew Adams
2023-10-30 7:44 ` Juri Linkov
2023-11-13 18:14 ` Drew Adams
2023-11-14 5:57 ` Thierry Volpiatto
2023-11-14 7:28 ` Juri Linkov
2023-11-05 18:11 ` Juri Linkov
2023-11-06 7:28 ` Juri Linkov
2023-11-09 16:34 ` Juri Linkov
2023-11-09 16:48 ` Eli Zaretskii
2023-11-09 17:03 ` Juri Linkov
2023-11-09 19:31 ` Eli Zaretskii [this message]
2023-11-10 7:45 ` Juri Linkov
2023-11-10 8:15 ` Eli Zaretskii
2023-11-12 8:13 ` Juri Linkov
2023-11-13 17:17 ` Juri Linkov
2023-11-13 18:14 ` Drew Adams
2023-11-14 7:30 ` Juri Linkov
2023-11-15 17:52 ` Juri Linkov
2023-11-10 19:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 6:19 ` Eli Zaretskii
2023-07-20 16:45 ` Drew Adams
2023-07-22 8:07 ` Eli Zaretskii
2023-07-16 13:40 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838r76zpsw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64656@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).