From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Andre Pang <andre@mindflux.com.au>, zsh-users@sunsite.auc.dk
Subject: Re: bug?
Date: Sat, 10 Apr 1999 20:17:57 -0700 [thread overview]
Message-ID: <990410201758.ZM16156@candle.brasslantern.com> (raw)
In-Reply-To: <19990410204844.A12932@drizzt.fl.net.au>
On Apr 10, 8:48pm, Andre Pang wrote:
} Subject: bug?
}
} andre@drizzt:~% echo $ZSH_VERSION
} 3.1.5
} andre@drizzt:~% zsh -e hello
} zsh: 12935 segmentation fault zsh -e hello
I believe this was fixed by the patch in zsh-workers/5305. With 3.1.5-pws-14,
I get:
zagzig<49> Src/zsh -e hello
hello: can't open input file: hello
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~1999-04-11 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-10 10:48 bug? Andre Pang
1999-04-11 3:17 ` 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=990410201758.ZM16156@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=andre@mindflux.com.au \
--cc=zsh-users@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).