From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu (Zsh workers list)
Subject: Re: Z-Shell Frequently Asked Questions (monthly posting)
Date: Thu, 25 Jul 1996 22:31:51 +0200 (MET DST) [thread overview]
Message-ID: <199607252031.WAA29799@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199607250812.KAA18570@sgi.ifh.de> from Peter Stephenson at "Jul 25, 96 10:12:11 am"
> From 3.0-pre3, [[, { and } are reserved words, hence must be
> separated from other characters by whitespace. (This change may
> be partially backed out since it breaks many scripts.)
I'm going to include this FAQ a little bit modified in pre4, patch included
below. It is not likely that the old [[ ... ]] behaviour will ever be
restored because it conflicts with the POSIX character class patterns like
[[:alpha:]].
Zoltan
*** /tmp/FAQ Thu Jul 25 22:22:34 1996
--- FAQ Thu Jul 25 22:22:38 1996
***************
*** 204,210 ****
completion. This version is known to have a bug with pipelines
inside other shell structures (now fixed in 2.6).
! The release of zsh 3.0 is imminent; currently 3.0-pre3 is available.
Major zsh sites are particularly encouraged to download this and
report any bugs. The new major number 3.0 largely reflects the
considerable internal changes in zsh to make it more reliable,
--- 204,210 ----
completion. This version is known to have a bug with pipelines
inside other shell structures (now fixed in 2.6).
! The release of zsh 3.0 is imminent; currently 3.0-pre4 is available.
Major zsh sites are particularly encouraged to download this and
report any bugs. The new major number 3.0 largely reflects the
considerable internal changes in zsh to make it more reliable,
***************
*** 1127,1134 ****
Changes since zsh 2.5:
From 3.0-pre3, [[, { and } are reserved words, hence must be
! separated from other characters by whitespace. (This change may
! be partially backed out since it breaks many scripts.)
The option CSH_JUNKIE_PAREN has been removed: csh-like code now
always does what it looks like it does, so `if ( ... ) ...'
executes the code in parentheses in a subshell. To make this
--- 1127,1135 ----
Changes since zsh 2.5:
From 3.0-pre3, [[, { and } are reserved words, hence must be
! separated from other characters by whitespace. From 3.0-pre4
! { and } work again without whitespace if the IGNORE_BRACES option
! is not set.
The option CSH_JUNKIE_PAREN has been removed: csh-like code now
always does what it looks like it does, so `if ( ... ) ...'
executes the code in parentheses in a subshell. To make this
next prev parent reply other threads:[~1996-07-25 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199607250812.KAA18570@sgi.ifh.de>
1996-07-25 15:42 ` Bart Schaefer
1996-07-25 20:31 ` Zoltan Hidvegi [this message]
1996-07-25 21:14 ` Bart Schaefer
[not found] <199701241329.OAA04769@hydra.ifh.de>
1997-01-26 11:50 ` gwing
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=199607252031.WAA29799@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=pws@ifh.de \
--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).