zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-users@math.gatech.edu
Subject: Chronology (was Re: %B%~%b bug in $PROMPT in 3.1.5 ?)
Date: Tue, 5 Jan 1999 08:52:56 -0800	[thread overview]
Message-ID: <990105085256.ZM9619@candle.brasslantern.com> (raw)
In-Reply-To: <199901051255.HAA03909@math.gatech.edu>

On Jan 5,  7:55am, Richard Coleman wrote:
} Subject: Re: %B%~%b bug in $PROMPT in 3.1.5 ?
}
} > Some years ago it became a goal of several of the most active zsh
} > contributors to make zsh capable of acting as a replacement for /bin/sh,
} > and particularly for ksh.  I griped about this repeatedly for some time,
} > but they had the support of the archive maintainer so I eventually gave
} > up and ignored zsh development for a long while.

I've been gently reminded that my chronology is flawed.  I did indeed quit
paying much attention to zsh from late 2.4 to late 2.6, but in reviewing
the situation I find that griping about ksh compatibility changes was what
got me involved again, not what drove me away.

Reviewing a few extremely old email messages, I find that it was setopt
incompatibilities that finally stopped me from using the later 2.4s and
on through 2.5.  Those setopt changes were designed to promote Bourne
shell (not ksh) compatibility, by disabling a number of csh features,
and caused syntax errors in many people's rc files at my site.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


       reply	other threads:[~1999-01-05 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199901051255.HAA03909@math.gatech.edu>
1999-01-05 16:52 ` Bart Schaefer [this message]
1999-01-05 17:17   ` Bruce Stephens
1999-01-05 17:55     ` 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=990105085256.ZM9619@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).