From: Jim <linux.tech.guy@gmail.com>
To: zsh <zsh-users@zsh.org>
Subject: Zsh requires Bash? 2002 revisited
Date: Sat, 6 Jan 2018 07:47:04 -0600 [thread overview]
Message-ID: <CA+rB6G+SJ+cojcoDgSAwM5PQAJhF_peVTyHbRYzrQ4ZTunNnCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Hi all,
After having to rebuild my system, I was unable to build zsh from
source. Web searches were getting me no where. Checking man
pages, guide, faq, and anything else I could think of reading, again
nothing. Since I have another life, besides zsh, I would come back
to this as time permitted. I finally found from the 2002 archives:
http://www.zsh.org/mla/workers/2002/msg00922.html
http://www.zsh.org/mla/workers/2002/msg00924.html Bart's reply.
Not exactly the same as back in 2002, but it was the key for me.
I had been testing different shells to be used as the default "sh" on
my system. The last one I was testing before starting zsh builds
was "posh". Out of the six shells(bash,dash,ksh,mksh,posh,zsh) I
have installed, posh is the only shell that fails in the same way as
described in the archives. Bad luck? Murphy's Law?
Not sure what can or should be done. I thought I would at least
report it. I just wish it had been easier to find.
Sincerely,
Jim Murphy
next reply other threads:[~2018-01-06 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 13:47 Jim [this message]
2018-01-06 17:23 ` Bart Schaefer
2018-01-06 20:36 ` Jim
2018-01-06 20:57 ` Bart Schaefer
2018-01-07 20:41 ` Jim
2018-01-06 21:21 ` Martijn Dekker
[not found] ` <4e96813d-3762-da35-f681-2546c0265982__30442.5932620235$1515274776$gmane$org@inlv.org>
2018-01-07 8:10 ` Stephane Chazelas
2018-01-07 20:40 ` Bart Schaefer
2018-01-07 8:48 ` Stephane Chazelas
2018-01-07 15:14 ` Stephane Chazelas
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=CA+rB6G+SJ+cojcoDgSAwM5PQAJhF_peVTyHbRYzrQ4ZTunNnCw@mail.gmail.com \
--to=linux.tech.guy@gmail.com \
--cc=linuxtechguy@gmail.com \
--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).