From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: zsh-workers-return-43578-ml=inbox.vuxu.org@zsh.org
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE
	autolearn=ham autolearn_force=no version=3.4.2
Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id ade77a06
	for <ml@inbox.vuxu.org>;
	Thu, 27 Sep 2018 22:38:40 +0000 (UTC)
Received: (qmail 14488 invoked by alias); 27 Sep 2018 22:38:23 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 43578
Received: (qmail 23238 invoked by uid 1010); 27 Sep 2018 22:38:23 -0000
X-Qmail-Scanner-Diagnostics: from mail-qk1-f172.google.com by f.primenet.com.au (envelope-from <mikachu@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.222.172):SA:0(-1.9/5.0):. 
 Processed in 3.902106 secs); 27 Sep 2018 22:38:23 -0000
X-Envelope-From: mikachu@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-transfer-encoding;
        bh=NoZaT37C4eK+/l8l2TTUUeWVwxAa0WE4IB/5g8ELEUc=;
        b=s2zwBzyUjvorkpmBybTzEFMwhUBaTNdX5u2XNwkN+EwdIk2yJX5X7nQOG4cuapGT/X
         PbKniUg0SL7ZGXyoDdcpgnQMH0NfqGlE3clPW2M9Vw28x01GuY7iC4aSKPVLdCxeRmzt
         3gKitdEU+4+JsOYAksWh7oN0hGR7IsRknhXW7HfUyisT4Qr2+5KZRQU1UAaA3LAJpzW0
         ltMImlEn4qRbTcKDqNkJXaNfpJ+Nr6NOW+Mudpz6aZCpMmiA7UgAbQ3RLC71x843zJ4K
         gsMR7MBRxHdvdP5skNDprUY8F01O+Pu01lArW6YQoJcqA8821yiWEk8KjsKP+Y2NKWag
         1uuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=NoZaT37C4eK+/l8l2TTUUeWVwxAa0WE4IB/5g8ELEUc=;
        b=VNQ0IVKe9RSH0AapYYjPYKrJh8IxbFNuuOpM3fw/seTdolLODvVp8JbVlKn1Bfa/LD
         oR0ZEoFa6hZiIY0lUOiZPiazE3m9YpwJvKdLeZs/jsd4HZz1rsCsqGZxKTD/qR4xtxkj
         2cyjYNym97dKTo9UZ31lMxUja9MhGbziHfhaw4t5caf5SZvw7NR1/OKmoNbUwvNaWyb2
         LghH2cL9lqhpkZvk4fP0VDq6B+1LkLzSk3n4+EXP6JPyoBK6fv7isr/PI6LRW1Zm9+kf
         FicHvTwm7puaQtp3oILj0668TMxcIK9FfC2J4v4L9B+9UHSYQIjVR/QaoM9LCFjWe9Fy
         0tNw==
X-Gm-Message-State: ABuFfoiGyCfdg+N/3sgkWdJWJAQbqH91UBSLwgW2/tKD1EVkujOF7XHw
	B5vvJwGVUY0xa6B21gAsjxPMpvS/CnoP0NjWlDc=
X-Google-Smtp-Source: ACcGV61GOssnlhQ6rkdfiyNtKpr9EXWiz4V/n9UTWfXINN6GTLxWAOh7wZB26OLWABgUpk6VfNQZNTC7juxo4OqKbfQ=
X-Received: by 2002:a37:d44c:: with SMTP id l73-v6mr9601156qki.190.1538087895938;
 Thu, 27 Sep 2018 15:38:15 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <16141d86-9d3e-275f-f7b4-d8b07fc97aa7@gmail.com>
References: <16141d86-9d3e-275f-f7b4-d8b07fc97aa7@gmail.com>
From: Mikael Magnusson <mikachu@gmail.com>
Date: Fri, 28 Sep 2018 00:38:15 +0200
Message-ID: <CAHYJk3QHUuxLXjot7mdy-Bo_HJ5u07Ex5=zspT6P7eyzfXc5AA@mail.gmail.com>
Subject: Re: `=' expansion causes script/subshell to exit, bug?
To: Vasiliy Ivanov <beelzebubbie.logs@gmail.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 27, 2018 at 9:20 PM, Vasiliy Ivanov
<beelzebubbie.logs@gmail.com> wrote:
> Hello. Recently I've seen that line like
>
> [[ -x =3Dsomebinary ]] || cmd
>
> causes script to exit unexpectedly with message like =C2=AB/path/to/scrip=
t:$line: =3Dsomebinary not found=C2=BB,
> instead of invoking || cmd and continue executing
>
> some simple tests:
>
> % ( [[ -x =3D123123 ]] || { print 'ohshi'; exit 2 } )
> zsh: 123123 not found <exit code 1>
>
> % ( b=3D123123; print =3D$b; print 'ohshi' )                             =
                     =E2=86=91
> zsh: 123123 not found
>
> Is it intended behaviour?
>
> % zsh --version
> zsh 5.6.2 (x86_64-pc-linux-gnu)

If you don't want to change any options, you can also use this
construct to avoid exiting without a subshell,

% { [[ -x =3Dsomebinary ]] } always { TRY_BLOCK_ERROR=3D0 } || echo hey
zsh: somebinary not found
hey

I also have this in my .zshrc
alias always_continue=3D'always { TRY_BLOCK_ERROR=3D0 }'
so I can do just
% { [[ -x =3Dsomebinary ]] } always_continue || echo hey
zsh: somebinary not found
hey

--=20
Mikael Magnusson