zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@ifh.de>, zsh-workers@math.gatech.edu
Subject: Re: Z-Shell Frequently Asked Questions (monthly posting)
Date: Thu, 25 Jul 1996 08:42:47 -0700	[thread overview]
Message-ID: <960725084247.ZM13255@candle.brasslantern.com> (raw)
In-Reply-To: Peter Stephenson <pws@ifh.de> "Z-Shell Frequently Asked Questions (monthly posting)" (Jul 25, 10:12am)

On Jul 25, 10:12am, Peter Stephenson wrote:
} Subject: Z-Shell Frequently Asked Questions (monthly posting)
}
} A4) What's the latest version?
} 
}   The release of zsh 3.0 is imminent; currently 3.0-pre3 is available.
} 
}   Note that even numbered minor versions are not released.

Um, 3.0 is an even-numbered minor version.  Are we revising this policy?

} B2) Similarities with csh
} 
}     Alternative syntax `if ( ... ) ...' (also `for', `which'; this now
}       requires the CSH_JUNKIE_PAREN option).

True only for 2.5.xx and some 2.6.xx.  CSH_JUNKIE_PAREN is gone again in
3.0, as you mentioned later.  However, you should probably point out that
`if ( ... ) ...' doesn't work like csh, it just looks like csh.  One still
has to replace the ( ) with [[ ]] in most csh-conversion cases.

-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"



       reply	other threads:[~1996-07-25 15:46 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 [this message]
1996-07-25 20:31 ` Zoltan Hidvegi
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=960725084247.ZM13255@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=pws@ifh.de \
    --cc=schaefer@nbn.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).