zsh-workers
 help / color / mirror / code / Atom feed
From: "Sebastian Höffner" <info@sebastian-hoeffner.de>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Feature request: Bash compliance
Date: Fri, 22 Jul 2016 19:40:03 +0000	[thread overview]
Message-ID: <CAJnbjpDbZ7jtZhyzZFBRvchWsCu7RyrVrEiwWjCouNecDYpbMg@mail.gmail.com> (raw)
In-Reply-To: <160722113554.ZM15595@torch.brasslantern.com>

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

Thanks Bart, it you are completely right.
Sadly even zsh wasabi.sh won't run it correctly, due to = expansion in the
first equality check as well as some array slicing problem in the very same
case/esac.
Thanks for looking into it!
Sebastian

On Fri, Jul 22, 2016 at 11:35 AM Bart Schaefer <schaefer@brasslantern.com>
wrote:

> On Jul 22,  3:51pm, Sebastian Hoffner wrote:
> } Subject: Re: Feature request: Bash compliance
> }
> } I ran into problems which are detailed here:
> } https://github.com/intuit/wasabi/issues/49 . My zsh is installed via
> } homebrew: zsh 5.2 (x86_64-apple-darwin15.4.0).
>
> torch% case this in
> case> this) echo now that;&
> case> that) echo this is that;;
> case> esac
> now that
> this is that
> torch%
>
> I would note that wasabi.sh begins with
>
>     #!/usr/bin/env bash
>
> which has the consequence that zsh is going to hand it off to bash even
> if your $SHELL is zsh, unless you are explicitly passing it to zsh with
> e.g. "zsh wasabi.sh".  So I think the problem here is all bash-3.2 and
> not zsh.
>

      reply	other threads:[~2016-07-22 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 18:22 Sebastian Höffner
2016-07-21 18:33 ` Bart Schaefer
2016-07-22 15:51   ` Sebastian Höffner
2016-07-22 18:35     ` Bart Schaefer
2016-07-22 19:40       ` Sebastian Höffner [this message]

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=CAJnbjpDbZ7jtZhyzZFBRvchWsCu7RyrVrEiwWjCouNecDYpbMg@mail.gmail.com \
    --to=info@sebastian-hoeffner.de \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@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).