From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22388 invoked from network); 26 Feb 2001 12:49:38 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Feb 2001 12:49:38 -0000 Received: (qmail 17029 invoked by alias); 26 Feb 2001 12:49:31 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13533 Received: (qmail 17017 invoked from network); 26 Feb 2001 12:49:26 -0000 Message-ID: To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Expanding interactively aliases In-Reply-To: Your message of "Mon, 26 Feb 2001 13:32:05 +0100." <200102261232.NAA18757@beta.informatik.hu-berlin.de> Date: Mon, 26 Feb 2001 12:48:57 +0000 From: Peter Stephenson > This is probably overkill... It's ten years too late to worry about that. I don't see any problem. Space for a couple of dozen lines of shell function no-one has to use isn't going to worry anyone (so long as the defaults make it work naturally, of course, which they do). > It alwasy tries to expand global aliases everywhere, maybe that should > be configurable, too. I can see an argument for being able to choose via a style. Then using tag aliases you can effectively make _expand_aliases into different commands/completers for completing or expanding command or global aliases. Now if you're *really* looking for overkill, there's the feature that aliases whose text ends with a space cause expansion of subsequent words as aliases... -- Peter Stephenson Software Engineer Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070