From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39636-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17630 invoked by alias); 14 Oct 2016 16:10:57 -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: 39636
Received: (qmail 1865 invoked from network); 14 Oct 2016 16:10:56 -0000
X-Qmail-Scanner-Diagnostics: from mail-wm0-f50.google.com by f.primenet.com.au (envelope-from <stephane.chazelas@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(74.125.82.50):SA:0(0.0/5.0):. 
 Processed in 0.306965 secs); 14 Oct 2016 16:10:56 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,
	T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1
X-Envelope-From: stephane.chazelas@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 74.125.82.50 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:mail-followup-to:references
         :mime-version:content-disposition:in-reply-to:user-agent;
        bh=Zj4LNWq23d5SwDj1EMDtOMOT0UG3grqr0CX/qcft/J8=;
        b=VnHjsDOjtLdvG4iSSIJHyQMhjOOyh31pS/u9NfWMF8Z7LpeUFuUxI0VL+LvbPYnc1r
         8sWCAtjHX0VtNOgL1yUPsZgUFbnyhLslvAPbFDcSr4M2A/EmIbTiNltTLhR75pvjLyaw
         cGqTVFY+frwBVgv0AlDxEmz5AtQ+oOI17LYM8uNCHxEjRF3jBGtmwy/VJ65wy6GvOWki
         W5z66rKawUKeOv1HaEyycAp72XY6LDhWP+oVxqKJDd53On8Rnpi/wMTWxCiPJRlC5fFT
         aVP5gTfUy5Jodl19SWcogDveMiVfLgVkDU8Ny/cyyrALDqEpPEPsNbuz9fU+wzqw2y4N
         zqdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to
         :references:mime-version:content-disposition:in-reply-to:user-agent;
        bh=Zj4LNWq23d5SwDj1EMDtOMOT0UG3grqr0CX/qcft/J8=;
        b=Qc3n/ldFE1KkHdsMHvjZqcSF5u6+vYkFIjp0S4XK8H6RsPzEF2w1sZIvZUc/cbCF/p
         Qm2pYo7w+BUSLXP5KiSR5ZFE98IqK7CSwkZFlCeLc8WgeGDxRfAQYAnOMzheUmTV5ZDy
         n2cgxdMA3DVAwMxa9pP2NU0bSbXVA7bER3jAQxYBDcZEciyKZH2np9+a2O5E1lHbOnAb
         LwL4sN2xBLTydc3A0DAJkg+pttzHAq5KnhxiPSEzUqi2fJxrrUVILspgx9pD+hAjR13p
         QJ1dE/zPvmFUaQq8CnmmBeblGL0qW39y76YoryKHbgjaBJto3+icLmuQzJotV/4K6rf2
         TLqw==
X-Gm-Message-State: AA6/9Rn0msSsKHm8YrMIovtlJrmaiBlO8XF1kiPmN3xqMTb6Ih5JOvwKy14Uj4aFBKDhfg==
X-Received: by 10.194.68.38 with SMTP id s6mr2535599wjt.130.1476461102157;
        Fri, 14 Oct 2016 09:05:02 -0700 (PDT)
Date: Fri, 14 Oct 2016 17:04:59 +0100
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [doc] $ERRNO broken
Message-ID: <20161014160459.GA17477@chaz.gmail.com>
Mail-Followup-To: Zsh hackers list <zsh-workers@zsh.org>
References: <20161014155603.GA17198@chaz.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161014155603.GA17198@chaz.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

2016-10-14 16:56:03 +0100, Stephane Chazelas:
> Probably unrelated to the $errnos issue raised recently. It
> looks like $ERRNO no longer works, at least on Debian Linux
> unstable amd64 with today's git code built with gcc 6.1 or gcc
> 4.4 or the zsh-5.2-5 Debian package.
> 
> Same on ubuntu 16.04 (5.1.1). It was fine in Ubuntu 14.04
> (5.0.2).
> 
> $ zsh -c '/; echo $ERRNO'
> zsh:1: permission denied: /
> 
> $ zsh -c 'typeset -p ERRNO
> $
[...]

Actually, it's fine when you *set* it beforehand, and you would
generally want to set it beforehand as in:

zsh -c 'ERRNO=0; /; echo $ERRNO'

or otherwise you wouldn't know what system call the $ERRNO you'd
get is from.

So it's just a documentation issue: the doc should say that
ERRNO should be set (declaring it is not enough) before use.

-- 
Stephane