9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Suggestion: Programming Tutorial for /sys/doc
Date: Fri,  2 Nov 2007 08:53:04 +0100	[thread overview]
Message-ID: <5d375e920711020053g1407d937n95a6a01c9c8692bb@mail.gmail.com> (raw)
In-Reply-To: <509071940711011844w6d2c8ff3r8046b40be55a30ce@mail.gmail.com>

> > The man pages have several flaws: there are too many;
>
> Again, I'm afraid I don't really understand this complaint. They are
> numerous, yes, because they're describing lots of different things.
> They don't make for the best introduction *on their own* for that
> reason, but they make an excellent reference - which is more or less
> their intent.

There is intro(2) is not a bad introduction either, althought it
certainly doesn't cover much.

Just thinking out loud here so I might make no sense, but I suspect
the issue is that the style of the plan9 documentation is very
different from what people have become used to expect, this days
people expects 'tutorials' and other handholding with many examples to
'copy paste' into their code and so on, which is quite different from
the Unix/Plan 9 documentation style of clear and concise information
and simple examples that help illustrate the general concepts, but
that does require the reader to actually *understand* things rather
than just follow an arbitrary set of steps.

Best wishes

uriel
>
> > some important stuff is hard to find;
>
> Sometimes, yes. lookman does a very good job, but is not perfect. Can
> you give examples of the types of difficulty you've been having?
>
> > "man page jumping" is a problem.
>
> Why? It's certainly easy enough to do - the acme integration via
> plumber is very nice. It's a "problem" in that it doesn't make for a
> nice, flowing introduction, but again, that's not their intent.
>
> My point about the man pages as regards an introductory document is
> mostly that it'd be bad to needlessly duplicate effort. I'd expect an
> introductory document to make extensive reference to the manual for
> the topics it covers.
>


  reply	other threads:[~2007-11-02  7:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 20:11 Pietro Gagliardi
2007-11-01 20:23 ` don bailey
2007-11-01 20:47 ` Anthony Sorace
2007-11-01 21:00   ` Pietro Gagliardi
2007-11-01 21:22     ` Federico Benavento
2007-11-02 13:10       ` Iruata Souza
2007-11-02 13:34         ` David Leimbach
2007-11-02 13:39           ` erik quanstrom
2007-11-02 16:44             ` geoff
2007-11-02 18:00               ` erik quanstrom
2007-11-02 19:34                 ` geoff
2007-11-02 20:57                   ` David Leimbach
2007-11-03  2:44                 ` Gorka Guardiola
2007-11-03  8:49                   ` Sander van Dijk
2007-11-03 15:24                     ` Eldanen
2007-11-03 21:43                       ` erik quanstrom
2007-11-03 23:40                         ` Eldanen
2007-11-06 14:39                         ` [9fans] Font Michaelian Ennis
2007-11-06 14:46                           ` Anant Narayanan
2007-11-06 14:50                             ` erik quanstrom
2007-11-07 18:12                               ` Michaelian Ennis
2007-11-06 14:56                           ` Martin Neubauer
2007-11-05 11:59                     ` [9fans] Suggestion: Programming Tutorial for /sys/doc Gorka Guardiola
2007-11-02 18:09             ` David Leimbach
2007-11-02 18:47         ` Pietro Gagliardi
2007-11-02 20:11           ` Iruata Souza
2007-11-02 18:52         ` Pietro Gagliardi
2007-11-01 21:27     ` Uriel
2007-11-02  1:44     ` Anthony Sorace
2007-11-02  7:53       ` Uriel [this message]
2007-11-01 21:24 ` ISHWAR RATTAN
2007-11-02  3:07 ` Joel C. Salomon
2007-11-02  8:19 ` fernanbolando
2007-11-02 10:03   ` roger peppe
2007-11-02 13:07     ` Eric Van Hensbergen
2007-11-02 12:42   ` erik quanstrom
2007-11-02 15:39 ` Douglas A. Gwyn
2007-11-02 19:12 ` Anant Narayanan
2007-11-02 19:44   ` Pietro Gagliardi

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=5d375e920711020053g1407d937n95a6a01c9c8692bb@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).