From: Clint Adams <schizo@debian.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Use of zerr() vs. zwarn()
Date: Sun, 1 Oct 2000 20:18:41 -0400 [thread overview]
Message-ID: <20001001201841.B12600@dman.com> (raw)
In-Reply-To: <1000929165834.ZM14923@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Fri, Sep 29, 2000 at 04:58:34PM +0000
> This would appear to be (as I suspected) a simple case of changing some
> calls to zerr() to be calls to zwarn() instead. However, there are a
> number of other places where zerr() is called that would have to change
> in order to generalize "builtins behave as if forked".
>
> There also seem to be a number of inconsistencies in whether zerr() or
> zwarn() is used for a particular condition. The following is an audit
> of places where I think the usage *might* need revision.
With current CVS and exec.c:2178 changed to zwarn, the failed redirection
from a builtin behaves as the failed redirection from a forked command, or
however that should be expressed in English.
I can't see any value to not doing it this way except perhaps in interactive
contexts, and even then it's a bit counterintuitive. I would expect something
like
echo blah blah blah >>logfile || echo log problem | mailx pagesomeone
to do the same thing as
/bin/echo blah blah blah >>logfile || echo log problem | mailx pagesomeone
next prev parent reply other threads:[~2000-10-02 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-27 19:46 two append bugs? Clint Adams
2000-09-28 3:35 ` Bart Schaefer
2000-09-29 16:58 ` Use of zerr() vs. zwarn() Bart Schaefer
2000-09-30 16:42 ` Bart Schaefer
2000-10-02 0:18 ` Clint Adams [this message]
2000-10-02 3:38 ` PATCH: First pass at zerr/zwarn sanity Bart Schaefer
2000-10-04 9:30 Use of zerr() vs. zwarn() Sven Wischnowsky
2000-10-04 9:47 ` Bart Schaefer
2000-10-04 11:53 Sven Wischnowsky
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=20001001201841.B12600@dman.com \
--to=schizo@debian.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).