From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10124 invoked from network); 19 Nov 2001 08:46:02 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Nov 2001 08:46:02 -0000 Received: (qmail 16626 invoked by alias); 19 Nov 2001 08:45:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16265 Received: (qmail 16614 invoked from network); 19 Nov 2001 08:45:47 -0000 Message-Id: <7D865FB0D0A1D5118B6E000347055BBB148489@G9JNT.mgb01.telekom.de> From: "Wischnowsky, Sven" To: zsh-workers@sunsite.dk Subject: Re: Local history Date: Mon, 19 Nov 2001 09:40:44 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Peter wrote: > I'm still thinking about a way of getting a local command history. My > particular use is so that zcalc and similar functions can > keep their own > data, separate from the main command history. [Not only does it break lines automatically, it also can't do that right...] I've been wishing for that, too, when I wrote the nslookup function. Bart came up with a solution using only fc and the parameters. but unfortunately that changed the numbers in the currently used history -- not really usable. I was thinking about doing it only at the very core, namely supporting more than one history list and a way (option to fc or something) to switch between these lists. One could then give them names and use $HISTFILE as the prefix of the filenames for the different histories (or support per-list flags saying if they are to be saved at all). That `sounded' not too complicated but I admit that I didn't really look into it. Maybe it's harder now with all this new history stuff I've not looked at yet. Bye Sven -- Sven wischnowsky wischnow@berkom.de