From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24592 invoked from network); 2 May 1998 20:32:15 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 2 May 1998 20:32:15 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id QAA00558; Sat, 2 May 1998 16:29:11 -0400 (EDT) Resent-Date: Sat, 2 May 1998 16:29:11 -0400 (EDT) From: Zoltan Hidvegi Message-Id: <199805022027.PAA09387@hzoli.home> Subject: foo(:...) and foo~ glob To: zsh-workers@math.gatech.edu (Zsh hacking and development) Date: Sat, 2 May 1998 15:27:13 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"RKtJb1.0.f8.M8uIr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3916 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu After this change: Sun Apr 5 20:00:40 1998 Andrew Main + parens always trigger globbing + with EXTENDED_GLOB, embedded `~' triggers globbing, as the documentation already states the (:quals) syntax no longer works. The idea was that foo(:...) should not do globbing if there are no wildcard, but it should execute the modifiers. This is very useful for general text manipulation. Of course ${${:-foo}:...} still works, but it's quite ugly. The other change related to ~ with EXTENDED_GLOB. Before ~ was only treated as exclusion character if it was not at the end of the word and the word contained other glob characters. This allowed you to write ls *~ rm foo~ dd if=~/foo of=bar etc. None of these work anymore. I know there was a special case for the (:...) stuff before in haswilds which was not very complicated. I know that someone else has also complained, so it's not only me. Zoli