From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34782-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 18913 invoked by alias); 26 Mar 2015 09:41:50 -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: 34782
Received: (qmail 22708 invoked from network); 26 Mar 2015 09:41:36 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
X-AuditID: cbfec7f5-b7fc86d0000066b7-f1-5513d44ab786
Date: Thu, 26 Mar 2015 09:41:04 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: PATCH: Removing aliases from history,
 2015 style (was capturing output of !! not working)
Message-id: <20150326094104.161af4d5@pwslap01u.europe.root.pri>
In-reply-to: <150325124032.ZM32185@torch.brasslantern.com>
References:
 <CACeGjnXH=Dk6eAv0OEfyT99RC9J=AMiyxL4wT4p_SVS1pLo0+g@mail.gmail.com>
 <20150319105716.620cd931@pwslap01u.europe.root.pri>
 <CACeGjnUxt0fZN2ArpV_8ECVF-_1KTtorO6rb11DzmOkOy3Xp4g@mail.gmail.com>
 <20150319125351.1e270c2d@pwslap01u.europe.root.pri>
 <20150320105703.2754b6af@pwslap01u.europe.root.pri>
 <150320090420.ZM21908@torch.brasslantern.com>
 <20150322183556.1fa0f143@ntlworld.com>
 <150322162235.ZM1728@torch.brasslantern.com>
 <20150323213426.21fd79c8@ntlworld.com>
 <20150325154853.7efc21d0@pwslap01u.europe.root.pri>
 <150325124032.ZM32185@torch.brasslantern.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsVy+t/xq7peV4RDDZ5f57Q42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGS8nLGEu2MlSsezjTaYGxl3MXYycHBICJhIPpt9jg7DFJC7c
	Ww9kc3EICSxllNhz7BUjhLOESeL0/7nsEM42RonF9/4BZTg4WARUJZ42Z4F0swkYSkzdNBss
	LCKgLdH+UQwkLCyQIXH39AlmkDCvgL3E40U1IGFOASuJ9mU3oCZeYpFYd62PFSTBL6AvcfXv
	JyaIg+wlZl45wwhi8woISvyYfI8FxGYW0JLYvK2JFcKWl9i85i3YM0IC6hI37u5mn8AoNAtJ
	yywkLbOQtCxgZF7FKJpamlxQnJSea6RXnJhbXJqXrpecn7uJERKyX3cwLj1mdYhRgINRiYc3
	QkkoVIg1say4MvcQowQHs5IIL+M54VAh3pTEyqrUovz4otKc1OJDjEwcnFINjEvmV+fmppx+
	npQe96St4tTz2SmMFTuDLy+cNEdrV2Xh5SfXppzq/mb2K6dv9UyH+hbFafvSHpVvF9xlcmv9
	LnEzdU/T8J2SCv7+kdqTT9btP7Axzc1Z5iWDkP3JL8XxeXxHGd428lgI3uCrMPomcNM4adcP
	xYPL4473xrWtdkvPPLNITLlohRJLcUaioRZzUXEiAOEH+vI3AgAA

On Wed, 25 Mar 2015 12:40:32 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> It may be appropriate to point out this tidbit:
> 
> torch% alias -g '&&'=foo
> torch% echo foo&&bar
> foo foobar

It's somewhat belatedly (sorry) occurred to me that the requirement to
use "-g" with this makes it unlikely there's any use case at all for
aliasing "&&".  The original one was to be able to do

  && stuff

by aliasing (not to "foo", obviously) at the start of an expression, so
it had its normal effect at the end.  You can't do that any more.

pws