From: Brian May <bam@snoopy.apana.org.au>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: [Brian May] zsh random behaviour
Date: Thu, 14 Jul 2005 13:44:02 +1000 [thread overview]
Message-ID: <sa43bqi6ohp.fsf@snoopy.microcomaustralia.com.au> (raw)
In-Reply-To: <1050711030705.ZM24700@candle.brasslantern.com> (Bart Schaefer's message of "Mon, 11 Jul 2005 03:07:04 +0000")
>>>>> "Bart" == Bart Schaefer <schaefer@brasslantern.com> writes:
Bart> On Jul 11, 11:32am, Brian May wrote:
Bart> }
Bart> } Is a return value of 255 treated specially by zsh?
Bart> A return value > 127 is interpreted as "killed by a signal"
Bart> where the signal number is the return value minus 127. This
Bart> is pretty standard for shells, though not well-documented by
Bart> any of them.
Bart> } I was about to start pulling my hair out, but I will let
Bart> you pull your } hair out instead <grin>.
Bart> See the "subtle 'echo' bug" thread from last month in the
Bart> zsh-workers archive, finishing with the patch in article
Bart> 21391.
I assume you mean the thread starting at
<URL:http://www.zsh.org/mla/workers/2005/msg00690.html>.
I am not sure how it is related, in this case there appears to be a
process (echo) writing its output to another process (echo) that never
reads it's stdin.
In my case though, one process is writing (or maybe not) to another
process (read) that always reads it's stdin. This second process is
suppose to return 1 if it gets EOF. So, AFAIK, SIGPIPE should not be
getting generated.
Or is it a matter that zsh is getting confused when the first process
returns 255, and aborts because it thinks the program was killed due
to a signal?
Also, there was the comment "...this only effects interactive shells",
but it my case I first encountered the problem in a shell script.
--
Brian May <bam@snoopy.apana.org.au>
next prev parent reply other threads:[~2005-07-14 3:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 1:32 Brian May
2005-07-11 3:07 ` Bart Schaefer
2005-07-14 3:44 ` Brian May [this message]
2005-07-14 9:38 ` Bart Schaefer
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=sa43bqi6ohp.fsf@snoopy.microcomaustralia.com.au \
--to=bam@snoopy.apana.org.au \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).