From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-3215-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 27445 invoked from network); 27 Jun 2000 00:08:15 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 27 Jun 2000 00:08:15 -0000
Received: (qmail 4462 invoked by alias); 27 Jun 2000 00:07:56 -0000
Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 3215
Received: (qmail 4454 invoked from network); 27 Jun 2000 00:07:54 -0000
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
Message-Id: <000626170342.ZM30180@candle.brasslantern.com>
Date: Mon, 26 Jun 2000 17:03:42 -0700
In-Reply-To: <20000626165550.I27070@tdc134.comm.mot.com>
Comments: In reply to Paul_A <acks@home.com>
        "HIST_ALLOW_CLOBBER and >&" (Jun 26,  4:55pm)
References: <20000626165550.I27070@tdc134.comm.mot.com>
X-Mailer: Z-Mail Lite (5.0.0 30July97)
To: Paul_A <acks@home.com>, zsh-users@sunsite.auc.dk
Subject: Re: HIST_ALLOW_CLOBBER and >&
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jun 26,  4:55pm, Paul_A wrote:
> Subject: HIST_ALLOW_CLOBBER and >&
> Is there any good reason why `|' doesn't get appended to >& in the history

I believe it's because of the e.g. >&3 syntax, which or course means "open
descriptor 1 as a copy of descriptor 3."  >&|3, on the other hand, means
"force open a file named '3' and direct descriptors 1 and 2 there".

This could probably be fixed at the cost of making the history code do more
complex parsing ...