zsh-users
 help / color / mirror / code / Atom feed
From: Zefram <zefram@dcs.warwick.ac.uk>
To: Christoffel@gmd.de (Juergen Christoffel)
Cc: zsh-users@math.gatech.edu (Z Shell users mailing list)
Subject: Re: Man pages missing
Date: Fri, 31 Jan 1997 12:51:15 +0000 (GMT)	[thread overview]
Message-ID: <13089.199701311251@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199701311236.AA30548@mail2.gmd.de> from "Juergen Christoffel" at Jan 31, 97 01:36:48 pm

Juergen Christoffel wrote:
>It started with tools like perl; I'm a regular perl user and would not
>want to miss it; but I remember the feeling I had when I first saw the
>30 or so pages of perl in the early days. And as the man pages grow
>larger it gets more difficult to locate a specific section because I
>can't browse the whole stuff anymore and to find it with a regexp I
>sometimes need two or three approaches to find stuff if I don't
>remember the exact wording I'm looking for.

perl's OK.  A quick look at perl(1) will generally indicate which man
page actually contains the desired information, which one can the drag
a regexp over.  It's the same with zsh, except that zshall(1) can be
used to skip the first step (provided, of course, you have a caching
(or exceptionally fast) man pager).

>There's no need to print out a manual if you don't want to. Today a
>hypertext approach would work for me due to tools like lynx (the vt100

Actually lynx uses curses; it's not limited to vt100s.

>based web browser, so you wouldn't need Netscape or its ilk) or Emacs'
>info mode. For me it's much more effective to browse through a well
>organized manual with lynx or emacs than it is to page through 60+
>pages of man pages with less.

For me, it's much more effective to have all the documentation in one
place, and browse it with my preferred pager.  Hypertext just gets in
the way of the information, and there still isn't a hypertext system
that formats to look as good as man pages.  (And have you ever tried to
read `all the documentation' on some subject, when said documentation
is arranged as an arbitrary directed graph of fifty nodes of two pages
each?)

-zefram


  reply	other threads:[~1997-01-31 13:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
1997-01-31 17:24 Karl E. Vogel

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=13089.199701311251@stone.dcs.warwick.ac.uk \
    --to=zefram@dcs.warwick.ac.uk \
    --cc=Christoffel@gmd.de \
    --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).