From: Dan Nelson <dnelson@allantgroup.com>
To: zsh-workers@sunsite.dk
Subject: Re: single manpage vs multiple files
Date: Wed, 26 Feb 2003 22:15:07 -0600 [thread overview]
Message-ID: <20030227041507.GB25640@dan.emsphone.com> (raw)
In-Reply-To: <20030227034129.GA21919@node1.opengeometry.net>
In the last episode (Feb 26), William Park said:
> What is the reason for separating Zsh manpage into several files? A
> single manpage (ie. man zsh) would be easier, no?
Hey, at least we're nowhere near as bad as perl!
(dan.2) /home/dan> man perl<TAB>
zsh: do you wish to see all 97 possibilities (25 lines)?
The only zsh manpage you really need is 'zshall', which is all the
little ones tacked together.
--
Dan Nelson
dnelson@allantgroup.com
prev parent reply other threads:[~2003-02-27 4:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 3:41 William Park
2003-02-27 4:05 ` Jason Price
2003-02-27 4:49 ` William Park
2003-02-27 7:37 ` Dan Nelson
2003-02-27 4:15 ` Dan Nelson [this message]
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=20030227041507.GB25640@dan.emsphone.com \
--to=dnelson@allantgroup.com \
--cc=zsh-workers@sunsite.dk \
/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).