From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: zsh 5.5 available
Date: Mon, 9 Apr 2018 20:02:14 -0700 [thread overview]
Message-ID: <7933b27f-eff4-7e19-54ba-77f9b0be0abe@eastlink.ca> (raw)
In-Reply-To: <20180410022902.al5jqjlhccsx5vlp@gmail.com>
On 09/04/18 07:29 PM, Joey Pabalinas wrote:
> On Mon, Apr 09, 2018 at 07:14:24PM -0700, Ray Andrews wrote:
>> Both info and man are still 5.3.1, what's needed to update them?
> Yodl is used to generate the documentation, and IIRC if the build
> system detects a Yodl install it should update the versions
> automatically.
>
I'd expect so but whereasthe 'info' is there, and I can run it " info
./zsh.info " if I'm in the directory where that file is found, otherwise
the older version is found. I ran " make install.info" and I have the
mentioned dependencies. Somehow 'info' just doesn't know where to
look. Ditto the 'man' pages-- still the older version. I copied
everything in the new build " .../share/man/man1" to "
/usr/share/man/man1", and that seems to work but I'd expect it to happen
automatically, as you say. Also, the specific info pages, inthe older
version seem to be just the man pages shown slightly differently, there
are no specific 'zsh.info*' files as there are with zsh-5.5, and I don't
know where they should go. There's a "/usr/share/info" directory but it
has no comparable files, only '...info.gz' files and I'm afraid to try
anything by hand.
next prev parent reply other threads:[~2018-04-10 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 16:45 Peter Stephenson
2018-04-08 22:06 ` Ray Andrews
2018-04-09 8:39 ` Peter Stephenson
2018-04-10 2:14 ` Ray Andrews
2018-04-10 2:29 ` Joey Pabalinas
2018-04-10 3:02 ` Ray Andrews [this message]
2018-04-10 3:35 ` Joey Pabalinas
2018-04-10 14:08 ` Ray Andrews
2018-04-10 15:54 ` Joey Pabalinas
2018-04-11 7:58 ` Simon Ruderich
2018-04-11 8:18 ` Peter Stephenson
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=7933b27f-eff4-7e19-54ba-77f9b0be0abe@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).