From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7552 invoked from network); 5 May 2000 15:03:44 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 May 2000 15:03:44 -0000 Received: (qmail 22426 invoked by alias); 5 May 2000 15:03:34 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11211 Received: (qmail 22028 invoked from network); 5 May 2000 15:03:01 -0000 From: "Bart Schaefer" Message-Id: <1000505150253.ZM694@candle.brasslantern.com> Date: Fri, 5 May 2000 15:02:52 +0000 In-Reply-To: <200005050853.KAA26324@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: nslookup input appears in history" (May 5, 10:53am) References: <200005050853.KAA26324@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: nslookup input appears in history MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 5, 10:53am, Sven Wischnowsky wrote: } Subject: Re: nslookup input appears in history } } Andrej Borsenkow wrote: } } > That's cool :-) } } I don't think so. } } That's why I said it would be nice if we could temporarily switch to a } different history in functions like nslookup. See zsh-users/2411. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com