From: Anthony Heading <aheading@jpmorgan.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
Mircea Damian <dmircea@secu.kappa.ro>,
zsh-workers@math.gatech.edu
Subject: Re: How to trigger the death of zsh(3.0.5)
Date: Fri, 18 Dec 1998 20:15:54 +0800 [thread overview]
Message-ID: <19981218201554.A16987@sin-emstar1.ny.jpmorgan.com> (raw)
In-Reply-To: <981008115831.ZM20784@candle.brasslantern.com>; from Bart Schaefer on Thu, Oct 08, 1998 at 11:58:31AM -0700
On Thu, Oct 08, 1998 (quite a long time ago!), Bart Schaefer wrote:
> A patch for this was posted to zsh-workers some while ago. You can find
> the article at:
>
> http://www.zsh.org/cgi-bin/mla/workers/bynum/4172
> [...]
>
> but you want the patch from 4172, not 4095. It should apply OK to 3.0.5
> even though the subject says 3.1.4.
I might have just made a mistake, but this didn't seem to apply cleanly to
3.0.5 at all. Has anybody got a 3.0.5 compatible patch? No problem if
not, I'll just go and work out what needs tweaked.
On a slightly more contentious note, I've lived with the odd crash till
now expecting that 3.1.5 would be worth switching to. But it was chock-full
of bugs, and the available fixes are now mixed up with dozens of new features.
These I would also live with, except that if recent history is any guide, Zefram
will autocratically remove those he doesn't like! (Who said history search??? :-)
So I can't really start to make use of them.
Granted, if I can't take the heat etc etc, there's always bash. But I think
it's unfortunate that the 'released' zsh crashes after every few hundred
commands, and it hasn't been fixed in six months or however long it is now.
Just the traditional 2c,
Anthony
parent reply other threads:[~1998-12-18 12:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <981008115831.ZM20784@candle.brasslantern.com>]
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=19981218201554.A16987@sin-emstar1.ny.jpmorgan.com \
--to=aheading@jpmorgan.com \
--cc=dmircea@secu.kappa.ro \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@math.gatech.edu \
/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).