From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <Peter.Stephenson@csr.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: intro.ms
Date: Fri, 13 Apr 2012 16:10:37 +0200 [thread overview]
Message-ID: <CAHYJk3ShtPWFZhqM3hM-wF4RwQ3zWvGHZQRvZ2MAPwzM_1XfRA@mail.gmail.com> (raw)
In-Reply-To: <20120413133524.076d7c74@pwslap01u.europe.root.pri>
On 13 April 2012 14:35, Peter Stephenson <Peter.Stephenson@csr.com> wrote:
> On Fri, 13 Apr 2012 14:21:27 +0200
> Mikael Magnusson <mikachu@gmail.com> wrote:
>> For more information, the files Doc/intro.txt or Doc/intro.troff
>> included with the source distribution are highly recommended. A list
>> of features is given in FEATURES, also with the source.
>>
>> But these files don't exist at least since we started using cvs, and I
>> can't get any man/troff/nroff/*roff variant to produce readable output
>> from intro.ms. /README notes that it is based on zsh 2.5 but still a
>> good introduction. Does anyone know how to build it, or should we
>> remove it and/or the recommendation to read it?
>
> "nroff -ms" is still producing quite readable about for me, and "pdfroff
> -ms" produced a usable document which we could distribute in the doc
> bundle, but it's not a very sensible source format. I suppose it would
> need to be translated by hand.
Ah, I didn't know you had to pass any switches to it, all I know about
roff is it's something to do with man pages usually :). I read about a
third of it so far, and most of it is still applicable. We might want
to remove the bits about compctl if we keep the recommendation in the
FAQ to read it.
--
Mikael Magnusson
next prev parent reply other threads:[~2012-04-13 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 12:21 intro.ms Mikael Magnusson
2012-04-13 12:35 ` intro.ms Peter Stephenson
2012-04-13 14:10 ` Mikael Magnusson [this message]
2012-04-13 22:42 ` intro.ms Peter Stephenson
2012-04-14 20:06 ` intro.ms Mikael Magnusson
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=CAHYJk3ShtPWFZhqM3hM-wF4RwQ3zWvGHZQRvZ2MAPwzM_1XfRA@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=Peter.Stephenson@csr.com \
--cc=zsh-workers@zsh.org \
/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).