zsh-workers
 help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: devs <zsh-workers@zsh.org>
Subject: Re: Possible missing status info for builtins sysopen and sysseek in zsh/system module
Date: Thu, 28 Apr 2022 08:50:08 -0500	[thread overview]
Message-ID: <CA+rB6GJfwNFmZJ5FZeMOJ_dMT3qD=Pr-sg4_x5a2Vqbf2+-q1w@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6G+8mEDS=iZztLCTbtK99MqmaG9chi_GWANOQ9HN_U1uMQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

Hi again,

On Thu, Apr 28, 2022 at 8:18 AM Jim <linux.tech.guy@gmail.com> wrote:

> Hi,
>
> Man page zshmodules(5.8) seems to be missing status information in module
> zsh/system for builtins sysopen and sysseek.  All the other builtins have
> some
> kind of statement for return status. I believe status 0 is success and 1
> would
> be an error of some kind for both. Don't know if there are other error
> numbers
> or if the parameter ERRNO is used.
>
> Should it be assumed 0 and 1 are the only status numbers if nothing is
> stated?
>

Can't assume that at least for sysseek.  If fd isn't assigned it returns a
status of 2.

Thanks,
>
> Jim Murphy
>

Jim

[-- Attachment #2: Type: text/html, Size: 1334 bytes --]

  reply	other threads:[~2022-04-28 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 13:18 Jim
2022-04-28 13:50 ` Jim [this message]
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
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='CA+rB6GJfwNFmZJ5FZeMOJ_dMT3qD=Pr-sg4_x5a2Vqbf2+-q1w@mail.gmail.com' \
    --to=linux.tech.guy@gmail.com \
    --cc=linuxtechguy@gmail.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).