From: "Ethan A. Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Argument lists in Plan 9 man pages
Date: Sun, 18 Mar 2018 10:07:53 +0000 [thread overview]
Message-ID: <1521367673.3679709.1307063336.6286C914@webmail.messagingengine.com> (raw)
In-Reply-To: <8ADDB08FEC580BCDA1A069F2B6469597@5ess.inri.net>
Seeing as this appears to be a thread for declaring opinion
along with an intent to do nothing, I may as well weigh in. ;)
On Thu, Mar 15, 2018, at 2:57 AM, sl@stanleylieber.com wrote:
>
> The argument against my point of view is that the man pages are
> supposed to be kept short enough, and programs should have few enough
> flag options, that it never becomes a problem wading through tens of
> paragraphs to locate the flag option you're looking for.
I formerly held to this opinion, with the exception that I never even tried
wading through more than 4 or 5 paragraphs at most. I have to admit
that even 2 paragraphs of verbiage around the options could be really
annoying at times.
I use the word "verbiage" because it sounds like "foliage", which in this
context reminds me of attempting to proceed through jungle undergrowth.
> Parsing the big paragraphs for flag options is
> cognitively disruptive and prone to error
Exactly.
I implied I'll do nothing at the top, but that may turn out to be false. I really
got back into programming in the last few weeks, but once I really got going
I found it somewhat addictive. There's always another fascinating puzzle to
solve, and I don't want to stop. Then, of course, it takes my energy away
from everything else. I decided to limit programming to one day a week,
but I need something lighter to fill the rest of my time.
I've got a few other things to write at the moment, but when they're done,
maybe I'll have a go at man pages.
--
The lyf so short, the craft so long to lerne. -- Chaucer
next prev parent reply other threads:[~2018-03-18 10:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-03-18 10:17 ` Ethan A. Gardener
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 1:25 sl
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
2018-03-18 10:15 ` 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=1521367673.3679709.1307063336.6286C914@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--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).