From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: ERRNO is unset until set
Date: Fri, 29 Apr 2022 17:08:05 +0000 [thread overview]
Message-ID: <6b0e70d7-c387-449d-a039-b7ec48f4fc07@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7ZOHoWBjcbBpWTS3uxZvmEkTzWAvsK4bUU5ictL=Kac_Q@mail.gmail.com>
Bart Schaefer wrote on Fri, 29 Apr 2022 17:02 +00:00:
> On Fri, Apr 29, 2022 at 3:00 AM Mikael Magnusson <mikachu@gmail.com> wrote:
>>
>> When is this good or useful?
>
> I was wondering that myself. The only thing I can think of is to make
> ${+ERRNO} show the "right" thing.
>
> Archive search is still offline (and I'm not sure it would help
> anyway) so I can't find the discussion that led up my patch from
> 32337,
https://zsh.org/workers/32157?
> but it seems to me that was intended to be just a first step to
> causing some of those variables to be non-special when zsh is started
> in emulation mode. The second step just never happened, or at least
> not comprehensively.
>
> I'm no longer even sure why ERRNO was included, there's no reference
> to it in the POSIX shell specification. Clash with some other shell?
> But which one?
next prev parent reply other threads:[~2022-04-29 17:08 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
2022-04-29 17:02 ` Bart Schaefer
2022-04-29 17:08 ` Daniel Shahaf [this message]
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=6b0e70d7-c387-449d-a039-b7ec48f4fc07@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--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).