From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
evgeny <illumsoft.org@gmail.com>,
git@vger.kernel.org
Subject: Re: t0005-signals.sh fails with ksh
Date: Sat, 9 May 2015 20:01:05 +0000 [thread overview]
Message-ID: <20150509200104.GB225482@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <20150508212146.GA16614@peff.net>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
On Fri, May 08, 2015 at 05:21:47PM -0400, Jeff King wrote:
> On Fri, May 08, 2015 at 02:16:19PM -0700, Junio C Hamano wrote:
> > I wonder if zsh is in the same league. Do we support people who do
> > SHELL_PATH=/bin/zsh and bend over backwards when it breaks?
>
> I tried "make SHELL_PATH=zsh test", but had trouble seeing the test
> output for all of the errors being spewed to stderr. ;)
>
> Certainly this:
>
> $ zsh ./t0000-basic.sh -v -i
> > [...]
> test_cmp:1: command not found: diff -u
> not ok 4 - pretend we have a fully passing test suite
>
> is not especially encouraging (it looks like running "$FOO bar" does not
> word-split $FOO). I am not a zsh user, though, so there may be ways to
> convince it to be more POSIX-y (e.g., just calling it as "sh").
I use zsh. It's possible to convince it to be more POSIXy by saying
"emulate sh" or invoking it via a symlink called sh. However, having
said that, I don't recommend it. I set /bin/sh to zsh on my Debian
system and a lot of things broke. Early versions of Mac OS X did that,
too, and they stopped because it was very broken.
As for ksh, I don't know whether you want to kill support for just ksh93
or mksh as well. I've generally had good experience with mksh as
/bin/sh when I've tried it, and it's at least semi-supported in Debian
because it meets Debian's POSIX-plus requirements.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-09 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 20:15 t0005-signals.sh fails with ksh evgeny
2015-05-08 20:34 ` Junio C Hamano
2015-05-08 20:55 ` Jeff King
2015-05-08 21:14 ` Jeff King
2015-05-08 21:39 ` Junio C Hamano
2015-05-08 23:43 ` evgeny
2015-05-09 8:20 ` Andreas Schwab
2015-05-08 21:16 ` Junio C Hamano
2015-05-08 21:21 ` Jeff King
2015-05-09 20:01 ` brian m. carlson [this message]
2015-05-08 23:05 ` evgeny
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=20150509200104.GB225482@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=illumsoft.org@gmail.com \
--cc=peff@peff.net \
/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.
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).