From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: zsh-users@sunsite.dk
Subject: Re: In the tla completion function: "${(@P)var_cmd-*:FILE:_files}"
Date: Fri, 20 Aug 2004 18:40:34 +0200 [thread overview]
Message-ID: <20040820164034.GB6405@s> (raw)
In-Reply-To: <Pine.LNX.4.61.0408200842470.27591@toltec.zanshin.com>
[Bart Schaefer]
>> Hmm, strange that my shell gives 'bad substitution' when
>> var_cmd is not defined.
> So does Jason's, I'm sure. Jason's point is that var_cmd should
> NEVER BE "not defined" in the _tla function. It's defined at the
> point where it's declared, to be the second word on the command
> line.
OK, now I get it; the '-' fallback doesn't test var_cmd, but
the variable named by the expansion of $var_cmd:
% unset foo
% var_cmd=foo
% echo "${(@P)var_cmd-*:FILE:_files}"
*:FILE:_files
--
Haakon
prev parent reply other threads:[~2004-08-20 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 21:32 Haakon Riiser
2004-08-17 0:52 ` Jason McCarty
2004-08-20 8:55 ` Haakon Riiser
2004-08-20 16:05 ` Bart Schaefer
2004-08-20 16:40 ` Haakon Riiser [this message]
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=20040820164034.GB6405@s \
--to=haakon.riiser@fys.uio.no \
--cc=zsh-users@sunsite.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).