From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26800 invoked from network); 28 Mar 2001 10:49:29 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 28 Mar 2001 10:49:29 -0000 Received: (qmail 194 invoked by alias); 28 Mar 2001 10:49:23 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13812 Received: (qmail 183 invoked from network); 28 Mar 2001 10:49:23 -0000 Date: Wed, 28 Mar 2001 12:49:22 +0200 (MET DST) Message-Id: <200103281049.MAA10490@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.dk In-reply-to: Wayne Davison's message of Wed, 28 Mar 2001 02:35:10 -0800 (PST) Subject: Re: Problem completing variables that contain spaces Wayne Davison wrote: > I noticed that the new completion code in the latest zsh code is > having trouble completing a variable that expands to a value that > contains spaces. For instance, I was trying to complete $PWD in > a directory path that contained a space: > > % mkdir 'two words' > % chdir 'two words' > % touch 1 2 > % ls -l $PWD/ > > Instead of $PWD remaining unexpanded and starting menu completion, it > expands to something strange like: > > $PWD/full/path/goes/here/two\ words/ > > This problem is not specific to PWD. I can't reproduce this. Can you try to make it do that starting with -f and tell us the setup? Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de