zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: build from source
Date: Fri, 2 Feb 2024 15:06:53 -0800	[thread overview]
Message-ID: <4dfbee91-257f-4e38-8a91-568dbf1d86fd@eastlink.ca> (raw)
In-Reply-To: <e00e33a9-c9be-49bc-b007-c17c161c31f0@eastlink.ca>

On 2024-02-02 08:14, Ray Andrews wrote:
> If the programme install-info is available, "make install.info" will
>
> insert an entry in the file "dir" in the same directory as the info ...
>
Weeell, all my info files are in '/usr/share/info' and they end in .gz 
and can't be viewed as text.  New zsh info files are in 
'/usr/local/share/info' all by themselves and they are viewable. ( .gz = 
zipped yes?  So info is happy either way it seems).

% info zsh'

... still shows 5.8 version, but

% info /usr/local/share/info/zsh

... shows 5.9 version.  Funny thing is that 'dir' in '/usr/share/info' 
has been updated so it would seem that it's anticipating an update to 
the main info tree, but all the files are old.  Is there a manual fix 
for this?  If not:

#zhelp() { info zsh $1 }
zhelp() { info /usr/local/share/info/zsh $1 }

... seems perfectly workable.





  parent reply	other threads:[~2024-02-02 23:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 22:31 Ray Andrews
2024-02-01 23:15 ` Bart Schaefer
2024-02-02  1:36   ` Ray Andrews
2024-02-02  2:08     ` Bart Schaefer
2024-02-02 16:14       ` Ray Andrews
2024-02-02 17:08         ` Oliver Kiddle
2024-02-02 18:13           ` Ray Andrews
2024-02-02 23:06         ` Ray Andrews [this message]
2024-02-03 22:27           ` Bart Schaefer
2024-02-03 23:42             ` Ray Andrews
2024-02-04  1:26               ` Lawrence Velázquez
2024-02-04  2:00                 ` Ray Andrews
2024-02-02  6:00     ` Lawrence Velázquez
2024-02-02 16:30       ` Ray Andrews

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=4dfbee91-257f-4e38-8a91-568dbf1d86fd@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).