zsh-workers
 help / color / mirror / code / Atom feed
From: Clive Messer <clive@epos.demon.co.uk>
To: schaefer@nbn.com
Cc: Zefram <A.Main@dcs.warwick.ac.uk>,
	Zoltan Hidvegi <hzoli@cs.elte.hu>,
	mdb@cdc.noaa.gov,
	Z Shell workers mailing list <zsh-workers@math.gatech.edu>
Subject: Re: zsh.texi commentary (actually, HTML pages commentary)
Date: Fri, 21 Jun 1996 18:22:49 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.3.94.960621180056.16353B-100000@epos.demon.co.uk> (raw)
In-Reply-To: <960621085558.ZM4927@candle.brasslantern.com>

On Fri, 21 Jun 1996, Bart Schaefer wrote:

> } > Why isn't ***/ mentioned anywhere?  That's like **/ except it follows
> } > symlinks, correct?
> } 
> } It is documented in the manual.
> 
> I know, but it isn't mentioned in the Filename Generation discussion of
> the .texi, and I think it should be.

Ok. That is fixed as well.

I will spend time this weekend checking the texi against the man pages, 
word for word. 

Bart: Please point your browser at:

	http://cust-www.easynet.co.uk/~epos/zsh_toc.html

where you will find the latest working copy. Please mail any 
errors/differences with it and the man-pages to _me_, rather than the
whole list, unless the error is also in the man page. 

> On Jun 21,  2:52pm, Zoltan Hidvegi wrote:
> } Subject: Re: zsh.texi commentary (actually, HTML pages commentary)
> }
> } But these changes should also be made in the manual.  Any voulnteers to
> } clean up the manual?  The texinfo and the nroff documentation should be
> } updated paralelly.  The manual also needs spell checking.  I'm quite busy
> } and I think I'm not the best in correcting sylistic problems in English.
> 
> I couldn't promise to have time, unfortunately.

Well, if no-one else is volunteering, I will see what time I have spare
over the weekend. 

(BTW, Re: spell checking ... 
Do we prefer American English or British English ? ;-)

Clive.
-- 
C Messer. Epos Systems. UK.  |
<clive@epos.demon.co.uk>     |   "I pressed her thigh and death smiled."
<clive@epos.easynet.co.uk>   |    Jim Morrison.                       




  parent reply	other threads:[~1996-06-21 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199606192106.XAA09696@bolyai.cs.elte.hu>
1996-06-19 23:42 ` zsh-2.6-beta21 released Clive Messer
1996-06-20 21:03   ` Mark Borges
1996-06-20 21:05     ` Zoltan Hidvegi
1996-06-21  7:30     ` zsh.texi commentary (actually, HTML pages commentary) Bart Schaefer
1996-06-21  8:06       ` Zefram
1996-06-21 12:15       ` Zoltan Hidvegi
1996-06-21 12:30       ` Clive Messer
1996-06-21 12:52         ` Zoltan Hidvegi
1996-06-21 15:55           ` Bart Schaefer
1996-06-21 16:59             ` Zefram
1996-06-21 17:22             ` Clive Messer [this message]
1996-06-21 17:32         ` Mark Borges
1996-06-21 17:45           ` 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=Pine.LNX.3.94.960621180056.16353B-100000@epos.demon.co.uk \
    --to=clive@epos.demon.co.uk \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=hzoli@cs.elte.hu \
    --cc=mdb@cdc.noaa.gov \
    --cc=schaefer@nbn.com \
    --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).