From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23615 invoked from network); 5 Jul 2000 06:26:45 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 Jul 2000 06:26:45 -0000 Received: (qmail 134 invoked by alias); 5 Jul 2000 06:26:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12168 Received: (qmail 127 invoked from network); 5 Jul 2000 06:26:37 -0000 Date: Wed, 5 Jul 2000 08:26:36 +0200 (MET DST) Message-Id: <200007050626.IAA10312@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Tue, 4 Jul 2000 17:15:51 +0000 Subject: Re: PATCH: Problem with _expand, _path_files, and $(command) Bart Schaefer wrote: > } I found another one: completion after something like `../$[4+]/' > [...] > } Blah. Very ugly. For now I had to add some $(print...)s, does anyone > } see a better solution? > > Yes: Use `eval'. `$(print -r ...)' won't do the right thing in the > array context, will it? For file names with embedded spaces, etc.? Argh, right. I just couldn't think of... > The one remaining problem is that zwarn() calls trashzle() even when > stderr has been redirected away from the terminal. Does anyone see a > problem with the utils.c patch below? ...this. Looks sensible. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de