From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Bug with exit status of zsh -c
Date: Sun, 19 Aug 2001 04:16:04 +0000 [thread overview]
Message-ID: <1010819041605.ZM16095@candle.brasslantern.com> (raw)
In-Reply-To: <1010814045738.ZM6709@candle.brasslantern.com>
On Aug 14, 4:57am, Bart Schaefer wrote:
}
} Is this really all that's necessary?
Nobody has said "boo" about this one way or the other -- my only worry,
really, is about the cases where last1 is supposed to be set to 2 -- so
I'm going to go ahead and commit it and we just have to be sure that it
has been tested before we release 4.0.3.
(For reference, I'm talking about zsh-workers/15617.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2001-08-19 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 1:46 Bart Schaefer
2001-08-14 4:57 ` Bart Schaefer
2001-08-19 4:16 ` Bart Schaefer [this message]
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=1010819041605.ZM16095@candle.brasslantern.com \
--to=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).