From: Vidiot <brown@ftms.COM>
To: zsh-users@math.gatech.edu (ZSH Mailing List)
Subject: Re: Man pages missing
Date: Thu, 30 Jan 1997 22:18:43 -0600 (CST) [thread overview]
Message-ID: <199701310418.WAA05535@ftms.ftms.com> (raw)
In-Reply-To: <3200.199701302328@stone.dcs.warwick.ac.uk> from "Zefram" at Jan 30, 97 11:28:09 pm
<>I'm sorry, but I can't find the *.man pages in the 3.1.1 release or the
<>zsh-doc release. For those of use who do not have, or don't want, yodl,
<>it would be nice if the *.man pages were really in the Doc directory.
<
<They are there, they're just called *.1 now.
There are no *.1 files in zsh-3.1.1. I did a find search and zippo files
that end in .1.
<The point of using yodl is that we only need to maintain *one* form of
<the manual. You now don't need to understand both nroff and TeXinfo to
<patch the man page. And the yodl is, I think, easier to maintain than
<either nroff or TeXinfo was.
Then I must be seeing things. The few .yo files that I sampled sure looked
like they had flavors of nroff and TeXinfo in them. It looks like this:
COMMENT(--- man page headers ---)
def(manpage)(4)(\
NOTRANS(.TH ")ARG1" "ARG2" "ARG3" "ARG4"\
)
def(manpagename)(2)(\
sect(NAME)NL()\
ARG1 - ARG2\
)
COMMENT(--- TeXinfo headers and conditionals ---)
def(texinfo)(2)(CMT())
def(texiifinfo)(1)()
def(texiiftex)(1)()
def(texititlepage)(0)(CMT())
def(texiendtitlepage)(0)(CMT())
def(texititle)(1)(CMT())
def(texisubtitle)(1)(CMT())
def(texiauthor)(1)(CMT())
def(texinode)(4)(CMT())
def(texitop)(1)(CMT())
COMMENT(--- section divisions ---)
def(chapter)(1)(CMT())
def(sect)(1)(\
USECHARTABLE(toupper)\
NOTRANS(.SH ")ARG1"NL()\
USECHARTABLE(standard)\
STDPAR()\
CMT()\
)
def(subsect)(1)(\
NOTRANS(.SS ")ARG1"NL()\
CMT()\
)
COMMENT(--- comment output ---)
DEFINECHARTABLE(roffcomment)(
'\n' = "\n.\\\" "
)
def(comment)(1)(\
USECHARTABLE(roffcomment)\
NOTRANS(.\" )ARG1\
USECHARTABLE(standard)\
)
To me this means one has to program yodl macros to handle nroff and texi
stuff (if something wasn't already defined).
In any event, I know n/t/groff and can muddle through TeX stuff. I'll
be damned if I am going to learn yodl. To learn yet another text processor
is just too much. So forgive me if I only send in changes to documentation
via quoting the current text and suggesting changes. If a format change
is needed, I will just have to indicate what needs to be done.
I can just hear it now... what a wimp. So be it. I have so many things I
have to know for my job, this is just one thing that breaks the camel's back.
MB
--
System Administrator - Finnigan FT/MS - Madison WI. <URL:http://www.ftms.com/>
e-mail: brown@ftms.com
phone: (608) 273-8262 ext: 612 fax: (608) 273-8719
Visit - <URL:http://www.cdsnet.net/vidiot/> (Your link to Star Trek and UPN)
next prev parent reply other threads:[~1997-01-31 4:40 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 [this message]
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
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=199701310418.WAA05535@ftms.ftms.com \
--to=brown@ftms.com \
--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).