From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Argument lists in Plan 9 man pages
Date: Sun, 18 Mar 2018 03:33:54 +0100 [thread overview]
Message-ID: <CAFSF3XO4P+k0ZFyc7xFVaZRE2q+HDUcNCsmoUw+a=Tv=OwsssA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1803171411240.47626@orthanc.ca>
neither are tutorials, but i would always recommend reading both to
get a good overview.
also: man pages are updated, /sys/doc stuff often is outdated.
earlier sl was correct to complain. what i really wanted to point out
is the significance of this additional use case, i.e. man pages cover
both a lot of detail (for quick references) and more abstract
overview.
On 3/17/18, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>> They are meant to be read also for getting an overview of the system.
>
> I think /sys/doc/* fulfills that role.
>
> Which isn't to say you can't learn a lot from reading manpages, but they
> aren't tutorials.
>
next prev parent reply other threads:[~2018-03-18 2:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 1:20 sl
2018-03-16 1:32 ` Lyndon Nerenberg
2018-03-16 13:22 ` hiro
2018-03-16 13:23 ` hiro
2018-03-16 15:08 ` Stanley Lieber
2018-03-16 15:45 ` hiro
2018-03-16 18:00 ` Stanley Lieber
2018-03-16 22:04 ` hiro
2018-03-16 22:06 ` hiro
2018-03-17 21:12 ` Lyndon Nerenberg
2018-03-18 2:33 ` hiro [this message]
2018-03-18 10:15 ` Ethan A. Gardener
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 1:25 sl
2018-03-15 2:57 sl
2018-03-15 3:33 ` Sean Hinchee
2018-03-15 3:34 ` Kurt H Maier
2018-03-15 4:54 ` Kyle Nusbaum
2018-03-18 10:07 ` Ethan A. Gardener
2018-03-18 10:17 ` Ethan A. Gardener
2018-03-15 1:53 sl
2018-03-15 2:19 ` [9front] " Kurt H Maier
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='CAFSF3XO4P+k0ZFyc7xFVaZRE2q+HDUcNCsmoUw+a=Tv=OwsssA@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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).