zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ifh.de>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: zsh-3.1.2-zefram4
Date: Mon, 20 Apr 1998 20:54:08 +0200	[thread overview]
Message-ID: <199804201854.UAA10269@hydra.ifh.de> (raw)
In-Reply-To: "Andrew Main"'s message of "Thu, 09 Apr 1998 10:25:25 MST." <199804090925.KAA19740@diamond.tao.co.uk>

just got back...

Andrew Main wrote:
> Peter's KSH_GLOB patch is included, but I backed out a lot of the changes.
> I'd like to have options affect as little as possible, preferably just one
> thing each: KSH_GLOB in this version *only* affects the interpretation
> of parens preceded by the magic characters (in fact, the option is
> only tested on one line of the source).  Parens *not* preceded by the
> magic characters are unaffected by the option.  Glob qualifies are also
> unaffected: that `-', mandatory with KSH_GLOB and forbidden without,
> was just too nasty to use.

The idea was that with the ksh and zsh models being incompatible
anyway, it was asking for trouble trying to mix them.  If you write
correct ksh scripts it won't be a problem, though, so it's fine by me.

> I also backed out the special handling of `(^...)', which changed
> the semantics of `^' in an extremely non-obvious way.  You can use
> `(^(...))' to invert the whole group.

?? It didn't have any semantics before, it didn't work at all inside
parentheses.  I can't remember what I did now (which is a bad sign),
but what's wrong with the meaning `negate the following' that it needs
the extra parentheses?

> This turned up a very old
> bug in the exclusion handling: `(foo~bar)BAZ' is actually treated as
> `fooBAZ~barBAZ', rather than the exclusion being properly localised.

?????? How could it possibly mean anything else?  What are parentheses
supposed to mean, anyway?  (foo|bar)BAZ is fooBAZ|barBAZ and in the
same way (foo~bar)BAZ is fooBAZ~barBAZ.  Or are you just referring to
the way it's evaluated in practice (which is as you say and could
therefore probably be simplified, but that doesn't make it a bug)?

-- 
Peter Stephenson <pws@ifh.de>       Tel: +39 50 844536
WWW:  http://www.ifh.de/~pws/
Gruppo Teorico, Dipartimento di Fisica
Piazza Torricelli 2, 56100 Pisa, Italy
 


  parent reply	other threads:[~1998-04-20 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <zefram@tao.co.uk>
1998-04-09  9:25 ` zsh-3.1.2-zefram4 Andrew Main
1998-04-10  3:21   ` zsh-3.1.2-zefram4 Richard Coleman
1998-04-10 13:00     ` zsh-3.1.2-zefram4 Louis-David Mitterrand
1998-04-16 16:35     ` New maintainer Andrew Main
1998-04-16 17:00       ` Richard Coleman
1998-04-10 16:08   ` zsh-3.1.2-zefram4 Andrej Borsenkow
1998-04-20 18:54   ` Peter Stephenson [this message]
1998-04-20 19:49     ` zsh-3.1.2-zefram4 Andrew Main
1998-04-21 11:36       ` zsh-3.1.2-zefram4 Peter Stephenson
     [not found] <19980409102529.13189.qmail@primenet.com.au>
1998-04-09 10:48 ` zsh-3.1.2-zefram4 Andrew Main
     [not found] <Pine.LNX.3.96.980409184105.1983B-100000@fruit.ml.org>
1998-04-09 16:55 ` zsh-3.1.2-zefram4 Andrew Main
1998-04-09 18:02 zsh-3.1.2-zefram4 Francisco Solsona
1998-04-11  1:24 zsh-3.1.2-zefram4 Gene Cohler
1998-04-14  9:33 ` zsh-3.1.2-zefram4 Andrew Main

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=199804201854.UAA10269@hydra.ifh.de \
    --to=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).