From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-13811-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 26662 invoked from network); 28 Mar 2001 10:30:56 -0000
Received: from sunsite.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 28 Mar 2001 10:30:56 -0000
Received: (qmail 23266 invoked by alias); 28 Mar 2001 10:30:49 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 13811
Received: (qmail 23250 invoked from network); 28 Mar 2001 10:30:48 -0000
Date: Wed, 28 Mar 2001 02:35:10 -0800 (PST)
From: Wayne Davison <wayned@users.sourceforge.net>
To: Zsh Workers <zsh-workers@sunsite.auc.dk>
Subject: Problem completing variables that contain spaces
Message-ID: <Pine.LNX.4.30.0103280228200.1718-100000@phong.blorf.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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/<TAB>

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.

..wayne..