From: Arthur Miller <arthur.miller@live.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal: ls-lisp.el handle --group-directories-first flag
Date: Sat, 24 Jul 2021 13:54:49 +0200 [thread overview]
Message-ID: <AM9PR09MB49776122EF2E8C0403D972FD96E69@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <83k0lgymsd.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Jul 2021 14:27:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 24 Jul 2021 14:13:09 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> > A think to note is that -U will be ignored if --group-directories-first
>> > is passed (so does gls).
>>
>> Hmm... bother: the need to add -U could be a problem, because users
>> don't necessarily want the list to come out unsorted.
>>
>> If adding -U is to fix the order of the directories, then how about
>> using nreverse on the list of directories instead?
True, I don't know why I didn't thought of it :-).
> Btw, in my testing, with ls-lisp-dirs-first bound non-nil, the
> directories are shown in their correct alphabetically sorted order.
> So I'm unsure what problems you saw and in which scenario. Can you
> tell more about this issue?
Ok, I'll test more.
> (Sorry about my slow responses, and thanks for working on this.)
No rush, it's not like this was something people complain about, and I
have seen all the tree-sitter work going on.
Have you seen the other patch, where flags are sanitized, that would
make ls-lisp accept all the flags as gnu ls, but ignore those it does
not undrstand. Provided that gnu ls does not use same flags as ls-lisp
with different meaning.
next prev parent reply other threads:[~2021-07-24 11:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 9:19 Proposal: ls-lisp.el handle --group-directories-first flag Arthur Miller
2021-07-16 11:57 ` Eli Zaretskii
2021-07-16 13:20 ` Arthur Miller
2021-07-16 13:44 ` Eli Zaretskii
2021-07-16 14:58 ` Arthur Miller
2021-07-17 11:57 ` Eli Zaretskii
2021-07-19 20:59 ` Arthur Miller
2021-07-24 11:13 ` Eli Zaretskii
2021-07-24 11:27 ` Eli Zaretskii
2021-07-24 11:54 ` Arthur Miller [this message]
2021-07-24 12:07 ` Eli Zaretskii
2021-07-24 14:58 ` Arthur Miller
2021-07-24 15:43 ` Eli Zaretskii
2021-07-24 19:02 ` Arthur Miller
2021-07-25 7:46 ` Eli Zaretskii
2021-07-25 8:29 ` Arthur Miller
2021-07-25 9:11 ` Eli Zaretskii
2021-07-25 9:31 ` Arthur Miller
2021-07-25 12:44 ` Michael Albinus
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=AM9PR09MB49776122EF2E8C0403D972FD96E69@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).