zsh-users
 help / color / mirror / code / Atom feed
From: Joey Pabalinas <joeypabalinas@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: zsh 5.5 available
Date: Mon, 9 Apr 2018 17:35:04 -1000	[thread overview]
Message-ID: <20180410033504.szcjo6zhpn4ggnix@gmail.com> (raw)
In-Reply-To: <7933b27f-eff4-7e19-54ba-77f9b0be0abe@eastlink.ca>

[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

On Mon, Apr 09, 2018 at 08:02:14PM -0700, Ray Andrews wrote:
> 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.

By default `make install` will install to /usr/local on most Linux
systems, and you probably don't have that in your MANPATH/INFOPATH.

You can either add /usr/local/share/man and /usr/local/share/info
to those environment variables or you can set the installation
paths when you ./configure with --prefix (currently you likely have it
as /usr/local) or you can set them individually with --mandir and
--infodir.

N.B. It's usually not a good idea to make install with --prefix=/usr
as that is the usual install prefix for you package manager and things
might get weird. I personally use --prefix=~/.local and have added the
paths in there to my .zshenv.

If you do it that way no need to use `sudo make install` either, just

> ./configure --prefix=~/.local && make && make install

and:

> MANPATH="$HOME/.local/share/man:$MANPATH"
> INFOPATH="$HOME/.local/share/info:$INFOPATH"

in your shell startup files

Also, the .gz files are just the gzipped versions which most man and
info (maybe all) implementations understand implicitly.

You can create them yourself if you want to safe space just by doing
`gzip foo.info` and decompress with `gzip -d foo.info.gz`

-- 
Cheers,
Joey Pabalinas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-04-10  3:35 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
2018-04-10  3:35           ` Joey Pabalinas [this message]
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=20180410033504.szcjo6zhpn4ggnix@gmail.com \
    --to=joeypabalinas@gmail.com \
    --cc=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).