From: Ralph Corderoy <ralph@inputplus.co.uk>
To: coff@tuhs.org
Subject: [COFF] Re: On Bloat and the Idea of Small Specialized Tools
Date: Sat, 11 May 2024 10:31:07 +0100 [thread overview]
Message-ID: <20240511093107.EC94C215AA@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAGg_6+Ov6hYTxQ5M-hEBoOiUQ0UVRP0V+aVi0STKAALLDUGY7g@mail.gmail.com>
Hi Nevin,
> the name "pr" doesn't really help me understand what it is for
As typical of the early commands, it's readily mnemonic.
PR(I) 3/20/74 PR(I)
NAME
pr - print file
SYNOPSIS
pr [-h header] [-n] [+n] [-wn] [-ln] [-t] [name...]
> How does one discover it?
Back then, by reading through the permuted index, turning the pages of
the printed manual, word of mouth... By making effort to learn the
profession's tools.
> If I have a command and I want it to do something slightly different,
> the first place I look is to see if there is a command line option for
> that. I know how to discover that (either --help or the man pages).
And a fine man page's SEE ALSO may help learn of new commands.
--
Cheers, Ralph.
next prev parent reply other threads:[~2024-05-11 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 16:36 [COFF] " Clem Cole
2024-05-10 23:02 ` [COFF] Re: [TUHS] " Steffen Nurpmeso
2024-05-11 9:18 ` [COFF] " Ralph Corderoy
2024-05-11 21:18 ` Steffen Nurpmeso
2024-05-11 21:33 ` Larry McVoy
2024-05-10 23:22 ` [COFF] Re: [TUHS] " Nevin Liber
2024-05-11 9:31 ` Ralph Corderoy [this message]
2024-05-11 12:51 ` John P. Linderman
2024-05-11 13:12 ` Dan Cross
2024-05-11 14:41 ` Bakul Shah via COFF
2024-05-11 15:45 ` Grant Taylor via COFF
2024-05-11 17:18 ` [COFF] " Ralph Corderoy
2024-05-11 21:35 ` [COFF] Re: [TUHS] " Theodore Ts'o
2024-05-12 7:13 ` Gergely Buday
2024-05-12 7:29 ` [COFF] " Ralph Corderoy
2024-05-12 22:23 ` Dave Horsfall
2024-05-11 19:24 ` [COFF] Re: [TUHS] " Clem Cole
2024-05-13 6:20 ` [COFF] " Arno Griffioen via COFF
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240511093107.EC94C215AA@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=coff@tuhs.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 NNTP newsgroup(s).