From: Josh Stern <jstern@citilink.com>
To: egcs@egcs.cygnus.com, espie@quatramaran.ens.fr
Subject: Re: (Getting rid of) man pages
Date: Fri, 30 Apr 1999 23:15:00 -0000 [thread overview]
Message-ID: <199904231809.NAA05842@foshay.citilink.com> (raw)
Message-ID: <19990430231500.nh60mkgPkVeFOXAnpu-BM9y9JZjyctJC7WzKQLFgM70@z> (raw)
If anyone ever introduces a replacement format for manpages,
it should be one that requires a sample of example usage (perhaps
listed at the bottom of the page, or accessible through a hyperlink)
for each of the major features of the utility in question
(this isn't a problem for pages that document APIs).
It would be an interesting thought experiment to try and estimate
the amount, in dollars, of productivity that could have been
saved by allowing people to quickly see examples of the major
syntactic forms and usage of utilities that they are not
familiar with - I think that a number described as "many billions"
would be an appropriate guess. It shouldn't matter whether
some originator thought of manpages as only a reminder for
the already initiated - in practice they have come to serve
as primary, and sometimes only documentation for the command line
interface on many systems.
- Josh
next reply other threads:[~1999-04-30 23:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 11:10 Josh Stern [this message]
1999-04-30 23:15 ` Josh Stern
-- strict thread matches above, loose matches on Subject: below --
1999-04-22 9:23 Gerald Pfeifer
1999-04-22 9:35 ` Alexandre Oliva
1999-04-30 23:15 ` Alexandre Oliva
1999-04-22 9:52 ` CaT
1999-04-22 10:08 ` Alexandre Oliva
1999-04-22 10:22 ` CaT
1999-04-30 23:15 ` CaT
1999-04-22 10:23 ` Keith Duthie
1999-04-22 10:26 ` CaT
1999-04-30 23:15 ` CaT
1999-04-22 10:31 ` Alexandre Oliva
1999-04-30 23:15 ` Alexandre Oliva
1999-04-22 16:10 ` Gerald Pfeifer
1999-04-22 16:44 ` Joe Buck
1999-04-22 22:19 ` Jeffrey A Law
1999-04-30 23:15 ` Jeffrey A Law
1999-04-23 1:52 ` Andreas Schwab
1999-04-23 9:12 ` Joe Buck
1999-04-24 0:31 ` rich-paul
1999-04-24 0:50 ` CaT
1999-04-30 23:15 ` CaT
1999-04-24 5:50 ` craig
1999-04-30 23:15 ` craig
1999-04-30 23:15 ` rich-paul
1999-04-30 23:15 ` Joe Buck
1999-04-23 10:52 ` Marc Espie
1999-04-23 11:00 ` Joe Buck
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Marc Espie
1999-04-30 23:15 ` Andreas Schwab
1999-04-30 23:15 ` Joe Buck
1999-04-30 23:15 ` Gerald Pfeifer
1999-04-30 23:15 ` Keith Duthie
1999-04-30 23:15 ` Alexandre Oliva
1999-04-30 23:15 ` CaT
1999-04-30 23:15 ` Gerald Pfeifer
1999-06-25 6:25 ` Alexandre Oliva
1999-06-30 15:43 ` Alexandre Oliva
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=199904231809.NAA05842@foshay.citilink.com \
--to=jstern@citilink.com \
--cc=egcs@egcs.cygnus.com \
--cc=espie@quatramaran.ens.fr \
/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).