From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Wesley Parish <wobblygong@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Thu, 21 Sep 2023 09:08:19 -0400 [thread overview]
Message-ID: <CAC0cEp-Wq7R1fXdEmB3fC2dT+dpf_CJKPzsntSibCcmek2Ua3A@mail.gmail.com> (raw)
In-Reply-To: <e5e2a65a-bd0d-4bef-4ad1-45df56a3fba9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
One of the things I liked about Mark Rochkind's original "Advanced UNIX
Programming" book was that he not only provided examples of what to do, but
also examples of what NOT to do, like failing to close the write end of a
pipe in a child that expects to read input. I'm not sure manual pages are
the right place for this sort of thing, but it certainly is valuable.
On Thu, Sep 21, 2023 at 12:10 AM Wesley Parish <wobblygong@gmail.com> wrote:
> On 21/09/23 10:31, Dave Horsfall wrote:
> > On Wed, 20 Sep 2023, Larry McVoy wrote:
> >
> > [...]
> >
> >> I like examples in man pages, I think it jump starts you into using the
> >> program more easily but maybe that's just me.
> > No, it's not just you :-)
> >
> > -- Dave
>
> Seconded. IDK when I was learning Linux, how many times I would've been
> unable to follow the reference in the Linux man pages without a
> reference example or more to show me how I could do it myself.
>
> Wesley Parish
>
>
[-- Attachment #2: Type: text/html, Size: 1411 bytes --]
next prev parent reply other threads:[~2023-09-21 13:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 20:32 [TUHS] " segaloco via TUHS
2023-09-19 23:39 ` [TUHS] " Larry McVoy
2023-09-20 1:26 ` segaloco via TUHS
2023-09-20 1:30 ` segaloco via TUHS
2023-09-20 14:57 ` Warner Losh
2023-09-20 15:40 ` Dan Cross
2023-09-20 2:09 ` Clem Cole
2023-09-20 2:25 ` Adam Thornton
2023-09-20 2:50 ` segaloco via TUHS
2023-09-20 19:56 ` Larry McVoy
2023-09-20 20:52 ` segaloco via TUHS
2023-09-20 22:31 ` Dave Horsfall
2023-09-21 4:09 ` Wesley Parish
2023-09-21 13:08 ` John P. Linderman [this message]
2023-09-21 0:26 ` Marc Donner
2023-09-21 3:06 ` Adam Thornton
2023-09-21 3:30 ` G. Branden Robinson
2023-09-21 3:48 ` Phil Budne
2023-09-21 13:37 ` Theodore Ts'o
2023-09-20 21:15 ` Alan Coopersmith
2023-09-21 3:49 ` G. Branden Robinson
2023-09-19 23:43 ` Adam Thornton
2023-09-20 13:23 ` Chet Ramey
2023-09-20 14:12 ` Alejandro Colomar (man-pages)
2023-09-19 23:47 ` KenUnix
2023-09-20 6:16 ` Jeremy C. Reed
2023-09-20 7:19 ` markus schnalke
2023-09-21 15:53 ` Kenneth Goodwin
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=CAC0cEp-Wq7R1fXdEmB3fC2dT+dpf_CJKPzsntSibCcmek2Ua3A@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=tuhs@tuhs.org \
--cc=wobblygong@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 NNTP newsgroup(s).