Re: The ls command
- To: debian-user@lists.debian.org
- Subject: Re: The ls command
- From: Nicolas George <george@nsup.org>
- Date: Wed, 5 Nov 2025 11:27:03 +0100
- Message-id: <[🔎] aQsmdzCa3KLlOcjw@phare.normalesup.org>
- Reply-to: debian-user@lists.debian.org
- In-reply-to: <aQVGvCpLGsMHis33@axis.corp>
- References: <20251030160422.GA29005@cventin.lip.ens-lyon.fr> <CAN+UU9peV-khbsakCcO+VMtAMo3Vki_mxnDFLtm9ebwn=SSiyA@mail.gmail.com> <aQOi1U8bqKy9k0SG@phcomp.co.uk> <20251031032606.GC957218@qaa.vinc17.org> <20251031034354.GK29520@wooledge.org> <CAMPXz=rUdJtvVRqLMtyuZyiJpuvNyAMxpkJt3Y7q5QsZbG0NKw@mail.gmail.com> <CAPU_E+fwnNge3dfkvF6c6u8=wppZ6QnKiFfjJNBLf6c39KuEmA@mail.gmail.com> <20251031112719.GL29520@wooledge.org> <aQS4sVFybeXu-d8E@phare.normalesup.org> <aQVGvCpLGsMHis33@axis.corp>
David Wright (HE12025-10-31):
> I'd agree with that, with the odd exception where the range of
> filenames is strictly limited. For example, ls -t1 is hard to
> beat for simplicity, compared with using find+printf+sort+cut
> or find+stat+sort+cut.
All if it is wrong. As soon as you print file names and read them back,
you are almost certainly doing it wrong, and more practically making
scripts that will fail under unusual circumstances.
Regards,
--
Nicolas George
Reply to: