From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9591 invoked from network); 2 May 2000 08:31:22 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 May 2000 08:31:22 -0000 Received: (qmail 17868 invoked by alias); 2 May 2000 08:31:13 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11050 Received: (qmail 17826 invoked from network); 2 May 2000 08:31:10 -0000 Date: Tue, 2 May 2000 10:31:08 +0200 (MET DST) Message-Id: <200005020831.KAA30064@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Mon, 1 May 2000 05:48:39 +0000 Subject: Shell-word splitting (was: Re: Proposed _history completer) Bart Schaefer wrote: > On Apr 28, 9:20am, Sven Wischnowsky wrote: > } > } Bart Schaefer wrote: > } > } > 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. > } > } [...] some parameter flag, most likely. Hm, s and S are taken, > } so are c and C. We could use `=' but that would probably be too > } irritating. > > Hrm. How would a parameter flag do this on an array? Parse each word > separately? I wrote this at the weekend (quite simple) and, yes, it just split the array's elements separately and then returned an array with all words from all elements. > Hrm, again; maybe the way to do this is with a modifier rather than a > flag. :S is available, and it'd be kinda fun to be able to apply this > to history as well as to parameters. Or maybe it wouldn't ... I'm withholding the patch I have because of this. I'll check how difficult this is to implement, but I guess it's equally simple. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de