zsh-users
 help / color / mirror / code / Atom feed
From: Zefram <zefram@dcs.warwick.ac.uk>
To: brown@ftms.COM (Vidiot)
Cc: zsh-users@math.gatech.edu
Subject: Re: Man pages missing
Date: Fri, 31 Jan 1997 11:45:48 +0000 (GMT)	[thread overview]
Message-ID: <5061.199701311145@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199701310418.WAA05535@ftms.ftms.com> from "Vidiot" at Jan 30, 97 10:18:43 pm

Vidiot wrote:
>There are no *.1 files in zsh-3.1.1. I did a find search and zippo files
>that end in .1.

Are we looking at the same file?

% tar tvzf zsh-3.1.1-beta.tar.gz | grep '\.1$'
-rw-r--r-- hzoli/operator   910 Dec 21 02:35 1996 zsh-3.1.1/Doc/ansi2knr.1
-rw-r--r-- hzoli/operator  7453 Jan 27 23:38 1997 zsh-3.1.1/Doc/zsh.1
-rw-r--r-- hzoli/operator   7444 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshall.1
-rw-r--r-- hzoli/operator  50450 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshbuiltins.1
-rw-r--r-- hzoli/operator  18455 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshcompctl.1
-rw-r--r-- hzoli/operator  34714 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshexpn.1
-rw-r--r-- hzoli/operator  41583 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshmisc.1
-rw-r--r-- hzoli/operator  26969 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshoptions.1
-rw-r--r-- hzoli/operator  25029 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshparam.1
-rw-r--r-- hzoli/operator  32860 Jan 27 23:38 1997 zsh-3.1.1/Doc/zshzle.1
% md5 zsh-3.1.1-beta.tar.gz
MD5 (zsh-3.1.1-beta.tar.gz) = f16415642314fe17d8c9c0c6823f56f4

>Then I must be seeing things.  The few .yo files that I sampled sure looked
>like they had flavors of nroff and TeXinfo in them.  It looks like this:
>
>COMMENT(--- man page headers ---)
> 
>def(manpage)(4)(\
>  NOTRANS(.TH ")ARG1" "ARG2" "ARG3" "ARG4"\
...

Bad choice of sample.  Look in the Zsh/ subdirectory, where the real
documentation is.

-zefram


  parent reply	other threads:[~1997-01-31 12:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-30 22:32 Vidiot
1997-01-30 23:14 ` Richard Coleman
1997-01-30 23:28 ` Zefram
1997-01-31  4:18   ` Vidiot
1997-01-31  4:57     ` Hrvoje Niksic
1997-01-31  5:47       ` Vidiot
1997-01-31  7:18         ` Hrvoje Niksic
1997-01-31 15:26           ` Vidiot
1997-01-31 16:10             ` James B. Crigler
1997-01-31 16:15             ` Bruce Stephens
1997-02-01 10:09             ` Hrvoje Niksic
1997-02-26 18:51             ` Juergen Erhard
1997-02-26 18:09               ` Uli Zappe
1997-02-27  0:11               ` man " Duncan Sargeant
1997-01-31 11:53         ` Man " Zefram
1997-01-31 12:36           ` Juergen Christoffel
1997-01-31 12:51             ` Zefram
1997-01-31 13:16               ` Bruce Stephens
1997-01-31 18:33               ` Juergen Christoffel
1997-02-01 10:03               ` Hrvoje Niksic
1997-01-31 16:11           ` Vidiot
1997-01-31 16:55             ` Zefram
1997-01-31 11:45     ` Zefram [this message]
1997-01-31 16:02       ` Vidiot
1997-01-31 16:18       ` Lee Eakin
1997-01-31 17:24 Karl E. Vogel

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=5061.199701311145@stone.dcs.warwick.ac.uk \
    --to=zefram@dcs.warwick.ac.uk \
    --cc=brown@ftms.COM \
    --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).