From: Hrvoje Niksic <hniksic@srce.hr>
To: zsh-users@math.gatech.edu (ZSH Mailing List)
Subject: Re: Man pages missing
Date: 01 Feb 1997 11:09:07 +0100 [thread overview]
Message-ID: <kigg1zgzvlo.fsf@jagor.srce.hr> (raw)
In-Reply-To: Vidiot's message of Fri, 31 Jan 1997 09:26:30 -0600 (CST)
(brown@ftms.com) wrote:
> <This is the approach some programs use (e.g. elm), and some not
> <(Perl, Emacs[1]). It is simply a matter of choice; I like the choice
> <zsh developers made.
>
> Perl is a bad example, since there are books available in your local book
> store. Zsh has no such book and really needs one.
No, it's not a bad example. When I say online documentation, I mean
it. I know I can always buy the book from the bookstore.
> <I don't see anything wrong with the "old-fashioned" help currently
> <used. Before thinking about converting to something different, one
> <should think about all the advantages of PDF over TexInfo? Is there a
> <freely available viewer for PDF files? Can they be viewed on a text
> <terminal?
>
> Advantages: graphical, can included visual examples (though I admit that there
> isn't much in the way of graphics :-); the user can scale the size of
> the help pages to suite the needs of the user; hypertext TOC and index;
> just to name a few.
Texinfo has almost all of this.
> Disadvantages: doesn't work on text-only systems (how many of these are
> still around
Then forget it. Yes, there are many text-only systems around, believe
it or not.
> (one shouldn't cripple the on-line help because of a lack of
> X-windows);
Remember; we're talking about the documentation of a Unix shell.
> I've used texinfo a few times and do not like the interface. One tends to
> hit the return key to move down lines. Well, that can't be done in texinfo
> help files (at least that is the way it used to be, is it still that way?).
You can always press `1 C-v', if you use Emacs. RET is used to follow
nodes.
> In any event one can argue about the best way for both systems. I personally
> prefer a physical copy of a manual.
It's quite easy to print out the Texinfo manuals. Thus we can have it
both ways -- you will have a nice, printed copy, and we'll be able to
browse it online.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Ask not for whom the <CONTROL-G> tolls.
next prev parent reply other threads:[~1997-02-01 10:17 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 [this message]
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
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=kigg1zgzvlo.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
--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).