From: "Pádraig Brady" <P@draigBrady.com>
To: Daniel Hofstetter <dhofstet@gmail.com>, 67765-done@debbugs.gnu.org
Subject: bug#67765: ls: manual entry for -f mentions incorrect option
Date: Mon, 11 Dec 2023 14:39:58 +0000 [thread overview]
Message-ID: <80cb09d6-1275-15a5-72ce-8eb66452e263@draigBrady.com> (raw)
In-Reply-To: <CAFRQvFq080aOdBLD_F6xa2XCvp3pPK3roLobdTkPQ=2+oWLrhA@mail.gmail.com>
On 11/12/2023 09:38, Daniel Hofstetter wrote:
> Hi,
>
> The manual entry for -f on
> https://www.gnu.org/software/coreutils/manual/html_node/Sorting-the-output.html#index-_002df-9
> contains:
>
> "[...] This is equivalent to the combination of --all (-a),
> --sort=none (-U), -1, --color=none, and --hyperlink=none [...]."
>
> The "-1" option seems to be incorrect because "ls -f" lists more than
> one file per line with ls 9.4.
Right, that description regressed in coreutils 9.0.
I've pushed a fix.
Marking this as done.
thanks,
Pádraig
prev parent reply other threads:[~2023-12-11 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 9:38 bug#67765: ls: manual entry for -f mentions incorrect option Daniel Hofstetter
2023-12-11 14:39 ` Pádraig Brady [this message]
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://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80cb09d6-1275-15a5-72ce-8eb66452e263@draigBrady.com \
--to=p@draigbrady.com \
--cc=67765-done@debbugs.gnu.org \
--cc=dhofstet@gmail.com \
/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.
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).