From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34688-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 10420 invoked by alias); 9 Mar 2015 17:03:25 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 34688
Received: (qmail 25868 invoked from network); 9 Mar 2015 17:03:23 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:message-id:date:in-reply-to:comments
         :references:to:subject:mime-version:content-type;
        bh=llpp/gwELiMs8UZ6OVWeriBe5xIj42fubnyCTmPj2us=;
        b=Iflqz0EdYJFVkqoZhB/zHcqwPeCRLL0rx5f09Y8Z1L7yChDTZ+JfAPSqTtjB54p57d
         E1hwx3cxwPvIBEGBuqW0MX/BZV1iRJ+y8fIRH+uc5E4JK7+Bq12NLYBWhL2UnLkEPwNH
         I/tUq7utDv99KJjBaSsa+JaX+7rOrHigcVKAv85BvugNvdMuwmP2AFeWMpjY64ZqHeOL
         GnGyMVMUgo18acFi4bvFSgFCdkvkQn5BKYakfu3jHNlufKKhfFDxPv9JvDAt/6wwFfUY
         lIwTYW/KfgiVOxdWPTzX2G7eN0/FpnQNAN0G8sKl7RxBTOxG6CQ1WERWJ/7HPrnwCcRl
         Gr5Q==
X-Gm-Message-State: ALoCoQm0yUmonLDZf7Z4QBqNWKGffKPieJpcezkJ4ZbU4+i2XOB9dtsLiXl7KC3ibd+8d/xM7Fnd
X-Received: by 10.202.188.66 with SMTP id m63mr21447429oif.14.1425920601888;
        Mon, 09 Mar 2015 10:03:21 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <150309100318.ZM12484@torch.brasslantern.com>
Date: Mon, 9 Mar 2015 10:03:18 -0700
In-Reply-To: <20150309163309.44a00910@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
        "Re: Aliasing separators (Re: grammar triviality with '&&')" (Mar  9,  4:33pm)
References: <20150304144756.GA27231@ypig.lip.ens-lyon.fr> 
	<150304175112.ZM19818@torch.brasslantern.com> 
	<20150305100638.55631238@pwslap01u.europe.root.pri> 
	<150305090720.ZM8441@torch.brasslantern.com> 
	<20150305174011.0be5a31e@pwslap01u.europe.root.pri> 
	<150305174240.ZM8732@torch.brasslantern.com> 
	<20150306094039.3d968c63@pwslap01u.europe.root.pri> 
	<150306112628.ZM9769@torch.brasslantern.com> 
	<20150307155252.75848f74@ntlworld.com> 
	<150307131008.ZM17180@torch.brasslantern.com> 
	<20150309114629.GF26461@xvii.vinc17.org> 
	<20150309163309.44a00910@pwslap01u.europe.root.pri>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: Aliasing separators (Re: grammar triviality with '&&')
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Mar 9,  4:33pm, Peter Stephenson wrote:
}
} What happens to white space certainly seems to be central to the things
} Bart is most worried about --- both what goes into and what comes out of
} the alias.  Possibly soluble with enough checks and management of
} token expansion.  Are we motivated enough to look into the necessary
} code to improve this?  We still have the option of backing it off
} before anyone outside the mailing list notices.

My vote (perhaps obviously) would be to back it out, fix the issue with
"{" / catenation and the history, and then consider whether aliasing of
other tokens can be re-introduced.