zsh-users
 help / color / mirror / code / Atom feed
From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-users@math.gatech.edu
Subject: Re: When the documentation will be updated?
Date: Mon, 03 Jul 1995 15:02:18 -0400	[thread overview]
Message-ID: <9507031902.AA01224@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Mon, 03 Jul 1995 13:29:54 EDT." <9507031729.AA02204@dragon.engineering>

>
>  Can I ask a question? When can we see the new documentation for zsh 2.6?
>

The man pages should generally be up to date.  The info files
and the introductory paper "intro.ms" are currently out of
date.  I will not have time to update them (unless someone
volunteers to help me on this) until right before the next
production release.  I will always keep the base document format
(which is currently the man pages) up to date as changes are
made.

I've looked at various ways to make it easier to keep all the
different formats up to date.  I've looked at using the pod format
(which the perl guys use for perl5) and sgml (which the linux
documentation project [LDP] uses), but they each lack something I
would like to have.  Currently I like best the sgml that the LDP uses,
but the disadvantage there would be that we would no longer have
man pages.  They have automatic converters to ascii text, html,
and postscript, but not man pages.  Since the documentation to zsh
has grown so big, this might actually be the best way to go, but
I'm still not sure.  I've also thought about putting the docs
in latex2e and just have postscript and ascii available.  This would
probably looked the nicest and could eventually lead to a book on
zsh (which I've considered writing).

What do you think?

Richard Coleman
zsh@math.gatech.edu


  reply	other threads:[~1995-07-03 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-07-03 17:29 Lung-Yung Chu
1995-07-03 19:02 ` Richard Coleman [this message]
1995-07-04 12:13   ` Anthony Iano-Fletcher

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=9507031902.AA01224@redwood.skiles.gatech.edu \
    --to=coleman@math.gatech.edu \
    --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).