From: Jukka Ruohonen <jruohonen@iki.fi>
To: discuss@mdocml.bsd.lv
Subject: Re: Lengthy documentation in mdoc
Date: Sun, 3 Jul 2011 19:09:48 +0300 [thread overview]
Message-ID: <20110703160948.GA17323@marx.bitnet> (raw)
In-Reply-To: <4E1054A5.2040903@bsd.lv>
On Sun, Jul 03, 2011 at 01:38:13PM +0200, Kristaps Dzonsons wrote:
> Sounds like more of a problem with the tools than the format. Can you
> imagine any ways to fix this? If anything constructive comes to mind,
> chime in and maybe it'll be worth some effort in mandoc-tools to field
> alternatives to mandoc | less.
Yes and no.
Partially this stems from the fact that large documents just are not that
well suited for a terminal. And partially this is caused by the BSD
man-page template that favors relatively short, concise documentation.
Something like uvm(9) or sysctl(7) are prime examples that presumably just
scare the potential readers away.
> On Sun, Jul 03, 2011 at 05:52:18PM +0200, Ingo Schwarze wrote:
> First time i heard that people are doing that on purpose,
> and i'd still consider it useless overhead. The introductory
> summary page will just keep people away from the real information,
> and reading one chunk, you have a hard time moving to another (let
> alone back).
No. It is exactly the opposite. See above.
> But even if we disagree on this finer point whether usability is
> better for small or large pages, i think we can agree that mdoc(7)
> is technically up to the job of dealing with both small and large
> pages.
I disagree. The mdoc.samples(7) (or equivalent) is not good for large
documents, and it has presumably never even meant to account such things.
> But for searching within a single page? I'd say the '/' command
> in less(1) is just fine.
Heh, I disagree also here. Searching with $PAGER has always been suboptimal.
Actually, Joerg's one old idea has been a sort-of small "man-page reader",
but that is another story.
> Looks like that server is completely dead:
Can not reproduce.
- Jukka.
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-07-03 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 19:36 Paul Onyschuk
2011-07-02 20:37 ` Ingo Schwarze
2011-07-02 21:14 ` Kristaps Dzonsons
2011-07-02 22:58 ` Paul Onyschuk
2011-07-03 9:31 ` Jukka Ruohonen
2011-07-03 11:38 ` Kristaps Dzonsons
2011-07-03 16:09 ` Jukka Ruohonen [this message]
2011-07-03 15:52 ` Ingo Schwarze
2011-07-05 12:24 ` Paul Onyschuk
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=20110703160948.GA17323@marx.bitnet \
--to=jruohonen@iki.fi \
--cc=discuss@mdocml.bsd.lv \
/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).