From: Jim <linux.tech.guy@gmail.com>
To: devs <zsh-workers@zsh.org>
Subject: zshall manpage
Date: Mon, 27 May 2019 06:25:56 -0500 [thread overview]
Message-ID: <CA+rB6GLD9nvb1dTvr23q2-Jv4ZMB9Bg_3AdH2m8CwwWx0NVcdw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
Hi devs,
Both zsh.1 and zshall.1 start with the following line:
¨Because zsh contains many features, the zsh manual has been split into
a number of sections¨
Then zsh.1 goes on to list:
zsh Zsh overview (this section)
zshroadmap Informal introduction to the manual
...
zshcontrib Additional zsh functions and utilities
zshall Meta-man page containing all of the above
Note: list item, zshall states ¨contains all of the above¨.
zshall.1 adds the following line before the list is given:
¨This manual page includes all the separate manual
pages in the following order:¨
Then zshall.1 goes on to repeat the list of man pages,
minus ¨zsh¨ and ¨zshall¨.
Question. Shouldn´t zshall.1 include ¨zsh¨ in the list of sections?
AFAICT ¨zsh¨ is included in zshall.1.
If you agree that it should the following patch would add it to the
list.
diff --git a/Doc/Zsh/intro.yo b/Doc/Zsh/intro.yo
--- a/Doc/Zsh/intro.yo
+++ b/Doc/Zsh/intro.yo
@@ -15,6 +15,9 @@ startlist()
index a7a2f3248..75d25ce27 100644
ifzshone(\
list(em(zsh) Zsh overview (this section))
)\
+ifzshall(\
+list(em(zsh) Zsh overview)
+)\
list(em(zshroadmap) Informal introduction to the manual)
list(em(zshmisc) Anything not fitting into the other sections)
list(em(zshexpn) Zsh command and parameter expansion)
Hope there aren´t any typos in the above patch as I am not currently
on a system I could copy and paste.
Appreciate your time, thanks,
Jim Murphy
next reply other threads:[~2019-05-27 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190527112716epcas1p29202e004dae55def56147644fcb72486@epcas1p2.samsung.com>
2019-05-27 11:25 ` Jim [this message]
2019-05-28 8:43 ` Peter Stephenson
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=CA+rB6GLD9nvb1dTvr23q2-Jv4ZMB9Bg_3AdH2m8CwwWx0NVcdw@mail.gmail.com \
--to=linux.tech.guy@gmail.com \
--cc=linuxtechguy@gmail.com \
--cc=zsh-workers@zsh.org \
/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).