From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: mattiase@acm.org, 36729@debbugs.gnu.org, stephen.berman@gmx.net
Subject: bug#36729: 27.0.50; Unclear total in directory listing
Date: Sun, 21 Jul 2019 19:43:35 -0700 (PDT) [thread overview]
Message-ID: <f5426445-0f86-4099-987d-a2481ec31ac2@default> (raw)
In-Reply-To: <<83k1care8v.fsf@gnu.org>>
> > Another good reason is that a given user's system
> > `ls' command might support switches and behavior
> > that ls-lisp does not support. That one you left
> > out, and it's the one that most directly concerns
> > ls-lisp. Ls-lisp is not, and likely will never
> > be, a complete replacement for all of the possible
> > `ls' commands out there.
>
> That is only true for some switches of GNU 'ls', AFAIK.
And perhaps not just GNU.
ls-lisp supports the `ls' switches that are common.
AFAIK, it doesn't claim to support every switch of
every `ls', even one being added tonight to some
system.
But if I'm wrong, and it commits to keeping up with
all systems that have `ls' and that might add a
switch (or change a switch's behavior), then more
power to it.
next parent reply other threads:[~2019-07-22 2:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<048FD91B-CDA0-4444-8F6F-C5B2F5C595CD@acm.org>
[not found] ` <<83k1ceusn1.fsf@gnu.org>
[not found] ` <<68D3B8E0-26F0-474A-B76D-320E523DBDDC@acm.org>
[not found] ` <<8336izsbok.fsf@gnu.org>
[not found] ` <<CFC507A0-42BE-40FF-AB46-3819B8714EB8@acm.org>
[not found] ` <<26fec456-c6bc-461f-8618-9cbc87cdde67@default>
[not found] ` <<83k1care8v.fsf@gnu.org>
2019-07-22 2:43 ` Drew Adams [this message]
2019-07-19 10:15 bug#36729: 27.0.50; Unclear total in directory listing Mattias Engdegård
2019-07-19 12:16 ` Eli Zaretskii
2019-07-19 13:28 ` Stephen Berman
2019-07-19 15:18 ` Drew Adams
2020-08-22 14:02 ` Lars Ingebrigtsen
2020-08-26 10:10 ` Stephen Berman
2020-10-07 4:44 ` Lars Ingebrigtsen
2020-10-07 7:50 ` Eli Zaretskii
2020-10-07 10:03 ` Mattias Engdegård
2020-10-07 12:14 ` Eli Zaretskii
2020-10-07 13:50 ` Mattias Engdegård
2020-10-07 14:23 ` Eli Zaretskii
2020-10-07 14:52 ` Mattias Engdegård
2020-10-07 16:40 ` Michael Albinus
2020-10-08 7:45 ` Robert Pluim
2020-10-08 8:37 ` Michael Albinus
2019-07-21 8:19 ` Mattias Engdegård
2019-07-21 14:29 ` Eli Zaretskii
2019-07-21 18:36 ` Mattias Engdegård
2019-07-21 21:31 ` Drew Adams
2019-07-22 2:32 ` Eli Zaretskii
2019-07-22 2:30 ` Eli Zaretskii
2019-07-26 18:30 ` Juri Linkov
2020-08-22 14:00 ` Lars Ingebrigtsen
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=f5426445-0f86-4099-987d-a2481ec31ac2@default \
--to=drew.adams@oracle.com \
--cc=36729@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
--cc=stephen.berman@gmx.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).