From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-11744-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 9760 invoked from network); 5 Jun 2000 04:48:25 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 5 Jun 2000 04:48:25 -0000
Received: (qmail 7857 invoked by alias); 5 Jun 2000 04:48:13 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 11744
Received: (qmail 7847 invoked from network); 5 Jun 2000 04:48:10 -0000
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
Message-Id: <1000605044800.ZM25052@candle.brasslantern.com>
Date: Mon, 5 Jun 2000 04:48:00 +0000
X-Mailer: Z-Mail (5.0.0 30July97)
To: zsh-workers@sunsite.auc.dk
Subject: Getting "parse error" from _path_files
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Cut'n'paste the following into a zsh-3.1.7:

echo "${(@)${(@s:|:)${(@)${(@f)$(< /etc/printcap)}:#[ 	\#]*}%%:*}%%[ 	]*}"
                                         
Note that inside each pair of [ ] are a space and a tab.

I get, at each tab:

_path_files:249: parse error

This is mildly annoying, as it aborts completion without giving the system a
chance to clean up (e.g., it's another case where very bad things happen if
it is _complete_debug that's called).  I vaguely recall forcing something
into a $(...) in some other completer to avoid a similar problem.

There are actually two things at issue here.  The second is that I'd rather
that completion didn't happen when I'm doing cut'n'paste.  I tried putting:

    (( PENDING )) && compstate[insert]=tab

near the top of _main_complete, right after curcontext is set up, and that
seems to help a bit, but I'm rather leery of that solution.  It does need
to use PENDING somehow, though.

Returning to the original issue:  Perhaps it would be possible to special-
case parsing within ${(e)...} so that errors of this sort simply return an
empty value for the parameter rather than aborting the whole call chain?
This would correspond to what happens when you use `eval', as in:

function fail() {
    local x y z
    x='${y'
    eval 'z=${(e)x}'
    echo got here
    z=${(e)x}
    echo did not get here
}

Alternately, of course, we could use `eval' on line 249 of _path_files and
in similar spots, but the quoting may sometimes get messy ...

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net