From: Dan Jacobson <jidanni@jidanni.org>
To: 70601@debbugs.gnu.org
Subject: bug#70601: join(1) info page -o: too hazy at first
Date: Sat, 27 Apr 2024 06:11:50 +0800 [thread overview]
Message-ID: <877cgj6aft.n.fsf@jidanni.org> (raw)
The join main page is really clear,
-o FORMAT
obey FORMAT while constructing output line
A base hit on the first pitch. The info page on the other hand,
‘-o FIELD-LIST’
‘-o auto’
If the keyword ‘auto’ is specified, infer the output format from
the first line in each file. This is the same as the default
output format but also ensures the same number of fields are output
for each line. Missing fields are replaced with the ‘-e’ option
and extra fields are discarded.
even after reading down to here, hasn't tipped the user off that it is
talking about the output format! It's its turn up to bat but it's still
drinking coffee in the bullpen.
In fact FIELD-LIST vs FORMAT make the user double check that they are
actually looking at the same commands' documentation.
reply other threads:[~2024-04-27 5:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=877cgj6aft.n.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=70601@debbugs.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.
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).