From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: ERRNO is unset until set
Date: Fri, 29 Apr 2022 12:00:11 +0200 [thread overview]
Message-ID: <CAHYJk3TQx057ZBM-6MogyJFOufsznj4SCWqmkyP4qr=DRfLm5Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Z=5fCZyNNXU8Fw1_OLzXF2P__gmX+pVUb3CcVvnn5JWg@mail.gmail.com>
On 4/29/22, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Thu, Apr 28, 2022 at 7:17 AM Matthew Martin <phy1729@gmail.com> wrote:
>>
>> Should have git blamed first. This was changed from 0 to PM_UNSET in
>> 32337 for emulation compatibility. Perhaps the docs should be updated
>> instead?
>
> We should at least be consistent.
>
> These code changes are pretty minor but perhaps shouldn't go in before
> the pending release.
Could you clarify how a script is helped by ERRNO not being listed,
but still being unusable for storing any data? eg,
% ARGV0=sh zsh
$ echo ${(t)ERRNO}
$ echo $ERRNO
$ ERRNO=hi
$ echo $ERRNO
0
$ echo ${(t)ERRNO}
integer-special
When is this good or useful?
--
Mikael Magnusson
next prev parent reply other threads:[~2022-04-29 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 13:18 Possible missing status info for builtins sysopen and sysseek in zsh/system module Jim
2022-04-28 13:50 ` Jim
2022-04-29 9:47 ` Jim
2022-04-28 14:07 ` ERRNO is unset until set Matthew Martin
2022-04-28 14:16 ` Matthew Martin
2022-04-29 6:44 ` Bart Schaefer
2022-04-29 10:00 ` Mikael Magnusson [this message]
2022-04-29 17:02 ` Bart Schaefer
2022-04-29 17:08 ` Daniel Shahaf
2022-04-29 17:19 ` Bart Schaefer
2022-04-29 17:13 ` grepping the archives (was: Re: ERRNO is unset until set) Daniel Shahaf
2022-04-30 0:45 ` Daniel Shahaf
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='CAHYJk3TQx057ZBM-6MogyJFOufsznj4SCWqmkyP4qr=DRfLm5Q@mail.gmail.com' \
--to=mikachu@gmail.com \
--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).