From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: [ANN] zsh-bin: statically-linked, hermetic, relocatable zsh
Date: Sun, 5 Apr 2020 20:57:12 +0200 [thread overview]
Message-ID: <CAN=4vMomRv-qSrQ=jEH+soygyzD1JjnyMnrPkSfJ112jwuhjxg@mail.gmail.com> (raw)
In-Reply-To: <28f42020-05b3-8420-2b4f-1780b541f0f2@eastlink.ca>
On Sun, Apr 5, 2020 at 8:48 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
> $ wget https://raw.githubusercontent.com/romkatv/zsh-bin/master/install
> $ ./install -d /aWorking/Zsh/Zsh-5.8
>
> 'man' was working but it was the old files, which I then deleted.
This is missing a few steps. How did you get to `man` after `./install`?
> It's all so compact now Roman, IMHO this is so much easier and more
> understandable.
Thanks!
I'd really like to get to the bottom of the issue with `man`. 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"
zsh
If so, could you provide some details about your system so that I can
reproduce it?
Roman.
next prev parent reply other threads:[~2020-04-05 18:58 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 [this message]
2020-04-05 19:15 ` Ray Andrews
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='CAN=4vMomRv-qSrQ=jEH+soygyzD1JjnyMnrPkSfJ112jwuhjxg@mail.gmail.com' \
--to=roman.perepelitsa@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).