From: Vinnie Shelton <shelton@icd.teradyne.com>
To: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.1.1 on NetBSD patch & problems
Date: Mon, 17 Feb 1997 18:48:46 -0500 [thread overview]
Message-ID: <199702172348.SAA20139@spacely.icd.teradyne.com> (raw)
In-Reply-To: coleman's message of Mon, 17 Feb 1997 18:03:14 -0500. <199702172303.SAA19445@redwood.skiles.gatech.edu>
RC wrote:
> I don't think this is a matter of backward compatibility, but
> more of a matter of creating a decent environment for new users.
Well, I hate to disagree with some who's trying to find common ground with
me, but I think it goes beyond the issue of creating a usable environment
for new users. Why should I have to add new cruft to my startup scripts
everytime a new release comes out? Why do we have to abandon things which
are already working? Why did I have to start using this function for pushd:
pushd () {
setopt localoptions globsubst
unsetopt ksharrays
case $1 in
+*) setopt pushdignoredups
builtin pushd ${${=$(dirs)}[$1+1]};;
-*) setopt pushdignoredups
builtin pushd ${${=$(dirs)}[$1-1]};;
*) builtin pushd $*;;
esac
}
[Thank you Peter and Bart.] Because people don't care about backward
compatibility. As Peter so aptly put it in article 2230:
It's yet another case of running very hard to stay in the same place.
So, Zefram, in answer to your rhetorical question: "I care".
> I realize most people on this list probably have a large list
> of compctl's, and override all the default ones. But this
> matter concerns new users rather than power users. What do
> we save by removing the default compctl's? Maybe 100 bytes, and
> a few micro-seconds of startup time.
>
> Zsh should (by default) start in a usable state. I hate tools that
> require extensive customization before they are usable. Let's not
> take zsh down that path.
RC, on this we do agree.
I'll get down off my soapbox now.
vin
next prev parent reply other threads:[~1997-02-17 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-17 6:49 gwing
1997-02-17 18:08 ` Zefram
1997-02-17 19:37 ` Vinnie Shelton
1997-02-17 19:47 ` Hrvoje Niksic
1997-02-17 20:38 ` Zefram
1997-02-17 23:03 ` Richard Coleman
1997-02-17 23:48 ` Vinnie Shelton [this message]
1997-02-19 14:23 ` gwing
1997-02-19 15:22 ` Zoltan Hidvegi
1997-02-19 17:24 ` Zefram
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=199702172348.SAA20139@spacely.icd.teradyne.com \
--to=shelton@icd.teradyne.com \
--cc=acs@acm.org \
--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).