From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24191 invoked from network); 28 Apr 2000 05:27:29 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 28 Apr 2000 05:27:29 -0000 Received: (qmail 8131 invoked by alias); 28 Apr 2000 05:27:17 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10988 Received: (qmail 8111 invoked from network); 28 Apr 2000 05:27:16 -0000 From: "Bart Schaefer" Message-Id: <1000428052522.ZM21808@candle.brasslantern.com> Date: Fri, 28 Apr 2000 05:25:22 +0000 In-Reply-To: <200004271044.MAA14334@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: Proposed _history completer" (Apr 27, 12:44pm) References: <200004271044.MAA14334@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: Proposed _history completer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 27, 12:44pm, Sven Wischnowsky wrote: } Subject: Re: Proposed _history completer } } Maybe we could make $historywords an assoc with the words as keys and } the values giving information about that word. Something like the } history number where it comes from plus information about the context } (command-context, of some kind). That can't work, can it? What if the same word appears in different places in the history, or even different places in the same command? The keys would have to be made unique somehow, or else you have to have a complicated format for compounding the value. I think having a way to chop a string into shell words -- something like what you did for copy-prev-shell-word -- would be more effective. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com