Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: HISTCHARS
- X-seq: zsh-workers 1161
- From: "Barton E. Schaefer" <schaefer@xxxxxxxxxxxxxx>
- To: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
- Subject: Re: HISTCHARS
- Date: Thu, 23 May 1996 13:40:31 -0700
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: Zoltan Hidvegi <hzoli@xxxxxxxxxx> "Re: HISTCHARS" (May 23, 8:32pm)
- References: <199605231832.UAA04182@xxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxxxxxxxxx
On May 23, 8:32pm, Zoltan Hidvegi wrote:
} Subject: Re: HISTCHARS
}
} A complete list of changes would be useful indeed.
The ones that I know of that make a difference to my zsh init files are
listed below. The version number at left is the earliest I know of
where the change showed up. I haven't tracked betas regularly since
sometime during 2.4 development, so I don't know the patch levels where
a lot of these showed up. Changes in features I don't use, aren't here.
2.1: Format of VERSION numbers changed from "X.0Y" to "X.Y".
Beta versions became "X.Ybeta Z".
2.4: Format of VERSION numbers changed from "X.Ybeta Z" to
"X.Y.Z beta". Broke all my carefully constructed tests,
created in .zshrc as I upgraded through 2.2 and dozens
of 2.3betas, for how a given zsh would behave.
2.5: Format of VERSION numbers changed from "X.Y" to "X.Y.ZZ".
At least this was relatively benign.
2.6: First, VERSION numbers changed from "X.Y.Z beta" to
"X.Y-betaZ". Next, VERSION variable became ZSH_NAME
and ZSH_VERSION. Broke all my tests *twice*. Make
up your minds, willya?
2.5: ${1}${2:+="$argv[2,$#]"} broke; something about the `='.
Intent is with argv=(foo bar baz), expand to foo="bar baz".
2.6: HOSTTYPE iris4d became irix?? where ?? is OS version.
Did other HOSTTYPEs change, too? I haven't compiled 2.6
on any other platforms yet, except Linux, for which I
have no earlier examples.
2.2: HISTCHARS="\!=#" broke; had to change to HISTCHARS="!=#".
2.6: HISTCHARS became histchars.
2.1: A whole bunch of new setopts:
KSH_OPTION_PRINT SUN_KEYBOARD_HACK PATHDIRS NOHUP
AUTO_MENU AUTO_REMOVE_SLASH
Previously (2.00) I'd just used MENU_COMPLETE.
2.5: CSH_JUNKIE_PAREN showed up, CSH_JUNKIE_TILDE went away.
This wouldn't have been a problem if CSH_JUNKIE_PAREN
had been *set* by default, rather than *un*set, but as
it was it broke every .zshrc in our entire organization.
We now setopt CSH_JUNKIE_PAREN in /etc/zshenv.
2.4: New options COMPLETE_IN_WORD ALWAYS_TO_END AUTO_PARAM_KEYS.
Zle gained push-line-or-edit.
2.6: Backslash handling in prompts and in `print -P` changed.
2.4: Namedirs got really stupid, and stayed stupid up to 2.5.
Second-most annoying change ever.
2.5: Option AUTO_NAME_DIRS fixed 2.4. Huge sigh of relief.
2.1: Prompt format %c started displaying too much of the path.
2.2: Prompt format %c got a number suffix to limit the number
of path components displayed.
2.3beta 90: Prompt format sequence %c2 changed to %2c (number suffix
became infix).
A couple of other changes that I recall are that SHLVL doesn't act the way
it used to (but I don't remember when that changed), and that "exec" causes
history files to be written (which I *really* can't stand). I believe the
SHLVL thing is "exec"-related too, come to think of it.
Something else changed between 2.3 and 2.5 that confused a bunch of scripts
we use here, forcing me to leave 2.3 installed on several machines just to
be able to run those scripts ... but I don't remember what it was. If I
figure it out I'll say something.
--
Bart Schaefer Vice President, Technology, Z-Code Software
schaefer@xxxxxxxxxx Division of NCD Software Corporation
http://www.well.com/www/barts http://www.ncdsoft.com/ZMail/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author