zsh-workers
 help / color / mirror / code / Atom feed
From: SL Baur <steve@xemacs.org>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh 3.0/3.1 bug, zsh 3.1.4 regression
Date: 19 Aug 1998 04:58:32 -0700	[thread overview]
Message-ID: <m24sv96v4n.fsf@altair.xemacs.org> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Wed, 19 Aug 1998 00:56:09 -0700"

Bart Schaefer <schaefer@brasslantern.com> writes:

> On Aug 18, 11:42pm, SL Baur wrote:
> } Subject: Re: zsh 3.0/3.1 bug, zsh 3.1.4 regression
> }
> } Please do not condemn those of us without true Bourne shells to
> } running bash as /bin/sh.  Things worked better in zsh-3.1.2 than they
> } do in either 3.1.3 or 3.1.4.

To be fair, I only tested 3.1.4 far enough to see that the $LANG
problem wasn't fixed, then didn't install it.  I'm running 3.1.3
(patched for the $LANG problem) as $SHELL and 3.1.2 as /bin/sh.

> You may think that, and may even have evidence of it, though I find
> 3.1.4 (plus a few recent patches) preferable to anything since 3.1 went
> off on its own development branch.

O.K.

> However, this particular detail ($^whatever) has been around since
> zsh 2.x,

Right.  I later recalled having older binaries laying around and found
2.6-beta20 exhibited the same behavior.

> with the only change being that before 3.0 it used to mean "toggle
> the option," which only made sense if you knew how the option was
> set to begin with.

I didn't know that.  O.K.

I didn't intend any criticism of the One True Shell, or of its
developers.  You've created a remarkable program I can't live
without and I'm only trying to help.


  reply	other threads:[~1998-08-19 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-18 18:19 SL Baur
1998-08-18 21:41 ` Bart Schaefer
1998-08-19  6:42   ` SL Baur
1998-08-19  7:36     ` Bart Schaefer
1998-08-19  7:56     ` Bart Schaefer
1998-08-19 11:58       ` SL Baur [this message]
1998-08-19 15:53         ` Bart Schaefer

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=m24sv96v4n.fsf@altair.xemacs.org \
    --to=steve@xemacs.org \
    --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).