From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: [ANN] zsh-bin: statically-linked, hermetic, relocatable zsh
Date: Sun, 5 Apr 2020 12:15:39 -0700 [thread overview]
Message-ID: <85eaccb0-2ad1-e9f1-cff1-67684d7c277d@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMomRv-qSrQ=jEH+soygyzD1JjnyMnrPkSfJ112jwuhjxg@mail.gmail.com>
On 2020-04-05 11:57 a.m., Roman Perepelitsa wrote:
>
> This is missing a few steps. How did you get to `man` after `./install`?
'Get to'? I just type the command:
$ man zsh
> I'd really like to get to the bottom of the issue with `man`.
I pride myself that if anyone can break something, I can ;-)
> It works
> for me on a dozen systems I've tried it on. Do these commands result
> in non-working `man zsh` for you?
>
> mkdir /tmp/zsh
> cd /tmp/zsh
> wget https://raw.githubusercontent.com/romkatv/zsh-bin/master/install
> sh ./install -d /tmp/zsh/zsh
> PATH="/tmp/zsh/zsh/bin:$PATH"
Ah ... I didn't change my path. I link to 'zsh' via a link in '/bin'
for simplicity's sake.
I'm pressed for time and will try the above a bit latter. Bet that's
it. Mind, nice to be able to leave
the path simple, so perhaps that can be considered. Does 'man' search
the path?
Back latter.
next prev parent reply other threads:[~2020-04-05 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 14:20 Roman Perepelitsa
2020-03-28 0:23 ` Ray Andrews
2020-03-28 10:37 ` Sebastian Gniazdowski
2020-03-28 14:02 ` Roman Perepelitsa
2020-03-28 16:06 ` Ray Andrews
2020-03-28 16:16 ` Roman Perepelitsa
2020-03-28 16:27 ` Ray Andrews
2020-04-05 15:46 ` Ray Andrews
2020-04-05 15:55 ` Roman Perepelitsa
2020-04-05 16:38 ` Ray Andrews
2020-04-05 16:45 ` Roman Perepelitsa
2020-04-05 18:47 ` Ray Andrews
2020-04-05 18:57 ` Roman Perepelitsa
2020-04-05 19:15 ` Ray Andrews [this message]
2020-04-05 19:19 ` Roman Perepelitsa
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=85eaccb0-2ad1-e9f1-cff1-67684d7c277d@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).