From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Getting "parse error" from _path_files
Date: Mon, 5 Jun 2000 10:04:08 +0200 (MET DST) [thread overview]
Message-ID: <200006050804.KAA03429@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 5 Jun 2000 04:48:00 +0000
Bart Schaefer wrote:
> 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.
It should then immediately return, too (to really avoid calling all
that completion code).
> 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 ...
How about a parameter flag, the opposite of `X', but used for `e' to
make it ignore parse errors and return an empty string in such cases?
Or make `e' not report errors normally and use `X' for `e', too, to
make it report errors?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-06-05 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 8:04 Sven Wischnowsky [this message]
2000-06-05 14:21 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-06-05 14:33 Sven Wischnowsky
2000-06-05 4:48 Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200006050804.KAA03429@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).