zsh-workers
 help / color / mirror / code / Atom feed
From: Richard Coleman <coleman@math.gatech.edu>
To: kpc@ptolemy-ethernet.arc.nasa.gov
Cc: zsh-workers@math.gatech.edu
Subject: Re: bug in zsh 2.6 beta 11
Date: Wed, 08 Nov 1995 21:52:46 -0500	[thread overview]
Message-ID: <199511090252.VAA04424@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Wed, 08 Nov 1995 18:42:44 PST." <9511090242.AA26529@phenotype.arc.nasa.gov>

> Thanks for confirming that the problems were not just mine.  Unless
> you need me to test it, instead of finding the patch in the list
> archives, I will wait for a later release.
> 
> I tried the patch you sent, and zsh now works under emacs but does not
> work under xterm.

In what way doesn't it work under xterm.  On what architecture? What OS?
After the subshell patch, what is going wrong?

> FWIW, I think that I have tried about 5 versions of zsh, including the
> most recent release and several recent betas, and that the only one I
> have gotten to work is 2.3.1.  Maybe things will stabilize when 2.6
> goes "gamma".  Anybody know when 2.6 will likely be released?  I am
> just looking for reliability and speed, since I am not a feature
> creature and I prefer not to attempt to hack on the zsh source.

I've given up trying to estimate when we will release the next production
version of zsh (which will be labeled zsh-3.0).  Since zsh has gotten a
reputation for being buggy, I want to make sure things are ultra-solid
before we make our production release.  Maybe in 3 or 4 months, but no
promises.

rc


  reply	other threads:[~1995-11-09  3:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-07 10:59 bug in zsh 2.6 beta 11: xkeysymdb kpc
1995-11-07 12:55 ` P.Stephenson
1995-11-07 15:42 ` bug in zsh 2.6 beta 11 Peter William Stephenson
1995-11-07 17:54   ` Vinnie Shelton
1995-11-07 20:01   ` Richard Coleman
1995-11-09  2:42   ` kpc
1995-11-09  2:52     ` Richard Coleman [this message]
1995-11-09  3:20       ` kpc

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=199511090252.VAA04424@redwood.skiles.gatech.edu \
    --to=coleman@math.gatech.edu \
    --cc=kpc@ptolemy-ethernet.arc.nasa.gov \
    --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).