From: Mark Borges <mdb@cdc.noaa.gov>
To: ZSH mailing list <zsh-workers@math.gatech.edu>
Cc: Clive Messer <clive@epos.demon.co.uk>
Subject: ZSH-3.0 web page prototype
Date: Wed, 17 Jul 1996 14:18:30 -0600 [thread overview]
Message-ID: <199607172018.OAA13287@suomi.cdc.noaa.gov> (raw)
I'm developing a prototype (very much a work in progress) for zsh-3.0
documentation at the URL,
http://www.mal.com/zsh3/
In an attempt to keep robots (and only robots) at bay, I've restricted
access to this development directory. To gain access, the username is
`zsh-workers' and the password is `falstad'. Hmm, I wonder if there
are robots that parse mail archives looking for passwords :-).
In particular, the zsh.texi (v2.1.1, as distributed with 3.0-pre3)
documentation translated to html via texi2html is now in
http://www.mal.com/zsh3/Doc/
(there is also a link from the old test URL).
I'm toying with the idea of having a frames version available, but it
pretty much sucks right now. A crude ugly version of the documentation
is in http://www.mal.com/zsh3/Doc/index-frame.shtml. But I'm thinking
of a three-frame window, with indices along the top, chapters along
the left, and the documentation itself in the main window, something
like:
--------------------------------------------------------
| | Indices go here |
|Chapter |---------------------------------------------|
|Names | |
|Here | |
| | |
| | main |
| | doc |
| | here |
| | |
| | |
|-------------------------------------------------------|
Anyway, all comments/suggestions are welcome, but my immediate concern
is the documentation and integrating it back into the FAQ (which still
refers to the old manual right now).
--
-mb-
next reply other threads:[~1996-07-17 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-17 20:18 Mark Borges [this message]
1996-07-17 23:30 ` Zefram
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=199607172018.OAA13287@suomi.cdc.noaa.gov \
--to=mdb@cdc.noaa.gov \
--cc=clive@epos.demon.co.uk \
--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).