From: "Richard J. Coleman" <coleman@math.gatech.edu>
To: Mark Borges <mdb@cdc.noaa.GOV>
Cc: ZSH mailing list <zsh-workers@math.gatech.edu>
Subject: Re: ZSH presence on WWW cf. Perl
Date: Fri, 15 Mar 1996 19:12:40 -0500 [thread overview]
Message-ID: <199603160012.TAA26873@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Fri, 15 Mar 1996 16:56:54 MST." <9603152356.AA07279@suomi.cdc.noaa.gov>
> With the release of perl-5.002 came a much better (IMO at least)
> organization. There are several aspects I like about it -- the broad
> categories, the update time-stamps, the diversions.
>
> I think it could serve as good boilerplate material for zsh. Not
> that there is anything seriously wrong with the zsh page at present
> -- it's certainly functional. But I'm getting bored with it.
Yes, these pages are very nice. Using them as a base for changes
to the zsh web pages is a good idea.
> In particular, I'd like to suggest that the baseline documentation be
> converted to something other than nroff, such as perlpod. Before you
> yell and flame back, wait...
I have looked at pod (and SGML, and other things) several times.
One of the things I don't like about pod, is that you can't put
things like boldface/italics in code examples. The zsh pages uses
this quite a bit.
I agree that nroff is terrible. I've been thinking maybe it's time
to scrap man pages altogether. Put all the documentation into a
latex file, and create a nice zsh manual.
rc
next prev parent reply other threads:[~1996-03-16 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-15 23:56 Mark Borges
1996-03-16 0:12 ` Richard J. Coleman [this message]
1996-03-18 8:30 ` Bas V. de Bakker
1996-03-18 8:47 ` Peter Stephenson
1996-03-18 15:44 ` Vidiot
1996-03-16 0:27 ` Chris Dean
1996-03-16 6:12 ` Zefram
1996-03-18 8:21 ` Bas V. de Bakker
1996-03-18 9:07 ` Zefram
1996-03-18 19:47 ` Mark Borges
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=199603160012.TAA26873@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=mdb@cdc.noaa.GOV \
--cc=zsh-workers@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).