zsh-users
 help / color / mirror / code / Atom feed
From: "Karl E. Vogel" <vogelke@c17mis.region2.wpafb.af.mil>
To: zefram@dcs.warwick.ac.uk
Cc: zsh-users@math.gatech.edu
Subject: Re: Man pages missing
Date: Fri, 31 Jan 1997 12:24:06 -0500 (EST)	[thread overview]
Message-ID: <199701311724.MAA29780@ss118.region2.wpafb.af.mil> (raw)

>> On Fri, 31 Jan 1997 12:51:15 +0000 (GMT), 
>> Zefram <zefram@dcs.warwick.ac.uk> said:

Z> For me, it's much more effective to have all the documentation in one place,
Z> and browse it with my preferred pager.  Hypertext just gets in the way of
Z> the information, and there still isn't a hypertext system that formats to
Z> look as good as man pages.

   Exactly.  Hypertext is fine when you're already familiar with most of what
   you're looking at, and all you need is to zoom in on a topic when more
   details are needed.

Z> And have you ever tried to read `all the documentation' on some subject,
Z> when said documentation is arranged as an arbitrary directed graph of fifty
Z> nodes of two pages each?

   Yes, and it drives me nuts.  That's when I either look for or create a
   PostScript version of the entire document.  It's generally easy to print
   them double-sided on HP LaserJets without fiddling with the printer console,
   and if I don't need to keep it, there's always a recycle bin around.

   I've never seen any hypertext system which lets me flip around as quickly or
   as easily as a 3-ring binder.  However, without a good keyword or concept
   index, it doesn't matter if the documentation is printed or not; I probably
   won't be able to find what I want either way.

-- 
Karl Vogel                                          vogelke@c17.wpafb.af.mil
ASC/YCOA, Wright-Patterson AFB, OH 45433	                937-255-3688


             reply	other threads:[~1997-01-31 18:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-31 17:24 Karl E. Vogel [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-01-30 22:32 Vidiot
1997-01-30 23:14 ` Richard Coleman
1997-01-30 23:28 ` Zefram
1997-01-31  4:18   ` Vidiot
1997-01-31  4:57     ` Hrvoje Niksic
1997-01-31  5:47       ` Vidiot
1997-01-31  7:18         ` Hrvoje Niksic
1997-01-31 15:26           ` Vidiot
1997-01-31 16:10             ` James B. Crigler
1997-01-31 16:15             ` Bruce Stephens
1997-02-01 10:09             ` Hrvoje Niksic
1997-02-26 18:51             ` Juergen Erhard
1997-02-26 18:09               ` Uli Zappe
1997-02-27  0:11               ` man " Duncan Sargeant
1997-01-31 11:53         ` Man " Zefram
1997-01-31 12:36           ` Juergen Christoffel
1997-01-31 12:51             ` Zefram
1997-01-31 13:16               ` Bruce Stephens
1997-01-31 18:33               ` Juergen Christoffel
1997-02-01 10:03               ` Hrvoje Niksic
1997-01-31 16:11           ` Vidiot
1997-01-31 16:55             ` Zefram
1997-01-31 11:45     ` Zefram
1997-01-31 16:02       ` Vidiot
1997-01-31 16:18       ` Lee Eakin

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=199701311724.MAA29780@ss118.region2.wpafb.af.mil \
    --to=vogelke@c17mis.region2.wpafb.af.mil \
    --cc=zefram@dcs.warwick.ac.uk \
    --cc=zsh-users@math.gatech.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).