From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33778-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 8524 invoked by alias); 23 Nov 2014 18:53:01 -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>
X-Seq: 33778
Received: (qmail 3187 invoked from network); 23 Nov 2014 18:52:49 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham
	version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=qb8OYlqdPyZrY6P7Ko4FKBHSh4IWgCWBxKnOUB6A6wY=;
        b=QqBq3IcNjbVZNC34vVs+NejndDzc4VnPpovoA3Ype2PIFW4Zrj9p4LWoNlogPL3tGE
         6mVU9pGy/uJwhy28r6hcUdcZwvEFBpp55V8V638eRAdCVm6syADYWJiRtyG8JDxSEvfJ
         QqxithVhZAcmrP2AUxMc01ZHINMUhl52ft8i43aM7SpxzCsD80UIcATFPz4LeClV3nKG
         SQfaTniTfObU+kGaEaupK80kY/Sb8AzQQPwzpDlbDtUAefAyHAp2MCuDBuzBxPUB0YXY
         faUySUocXAVD4AEcUWHRcHTSmb5t90mzPj/3LaFS1jbE6Glkz1JFvrpJukNcUPc4jUJ2
         /JDw==
MIME-Version: 1.0
X-Received: by 10.42.25.144 with SMTP id a16mr14447943icc.66.1416768767741;
 Sun, 23 Nov 2014 10:52:47 -0800 (PST)
In-Reply-To: <141123101345.ZM10525@torch.brasslantern.com>
References: <5470C427.4050805@thequod.de>
	<CAHYJk3S5pBBNnAKqyGRYq7KAstpSAJOPQRdbHjoKrurLKFbOcQ@mail.gmail.com>
	<5470CF7C.2000707@thequod.de>
	<CAHYJk3R81LhwfwxaDHRSMP0HZmbE7V3hrrn5Q4jGzRzBPRC=oQ@mail.gmail.com>
	<5472040F.8020803@thequod.de>
	<141123101345.ZM10525@torch.brasslantern.com>
Date: Sun, 23 Nov 2014 19:52:47 +0100
Message-ID: <CAHYJk3QgA-kXfeCT+dAEdF4u6eQtCZRss39UjA2Rqm2=XPCa_w@mail.gmail.com>
Subject: Re: BUG: failure in "vcs_info prompt" aborts precmd function
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On Sun, Nov 23, 2014 at 7:13 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Nov 23,  4:58pm, Daniel Hahler wrote:
> } Subject: Re: BUG: failure in "vcs_info prompt" aborts precmd function
> }
> } On 22.11.2014 23:20, Mikael Magnusson wrote:
> }
> } >> Apart from that, I am still wondering why the error in vcs_info causes abortion of the precmd function?!
> } >
> } > Passing a non-existing file to $(< is a fatal error, or whichever term
> } > is correct here.
> }
> } I got that, but e.g. `false` does not abort the precmd function.
>
> "false" is just a normal command that returns nonzero.
>
> $(<notafile) is treated similarly to a syntax error, it kills the whole
> surrounding context.
>
> It's pretty easy to make it behave like a failed external command; can
> anyone recall why it wasn't, other than to avoid allocating an empty
> linked list?  It has been a fatal error since before revision control
> was in use.  It is possible something really depends on being stopped
> by this error?

Maybe it predates the UNSET option and nobody ever caught it? compare eg,
% ( setopt nounset; echo $a; echo hello )
zsh: a: parameter not set
% ( echo $(< foo); echo hello )
zsh: no such file or directory: foo

It is sort of a parameter expansion, after all.

-- 
Mikael Magnusson