From: "Jérémie Roquet" <arkanosis@gmail.com>
To: zsh-workers@zsh.org
Cc: Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: zle messes up 'words' variable?
Date: Wed, 27 Apr 2011 11:02:54 +0200 [thread overview]
Message-ID: <BANLkTik=Jvvp+af1Zg3487VFQ_7HZyRJ_Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik3BGrNd389-cDELWwdqR_LZ-qgOA@mail.gmail.com>
Hi,
2011/4/27 Felipe Contreras <felipe.contreras@gmail.com>:
> I'm trying the following:
> ---
> set_vars ()
> {
> cur="foo"
> words="foo"
> cwords="foo"
> }
>
> _foo ()
> {
> local cur words cwords
> set_vars
>
> echo "cur=${cur} words=${words} cwords=${cwords}" >> /tmp/comp_test.txt
> }
>
> compdef _foo foo
> ---
>
> Which results in:
> cur=foo words= cwords=foo
>
> Strangely enough, if I use the #compdef tag, the code works fine (words="foo").
>
> Any ideas?
$words is a special array used for completion. See `man zshcompsys'
for more about it.
Best regards,
--
Jérémie
next prev parent reply other threads:[~2011-04-27 9:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 8:26 Felipe Contreras
2011-04-27 9:02 ` Jérémie Roquet [this message]
2011-04-27 9:11 ` Felipe Contreras
2011-04-27 9:51 ` Felipe Contreras
2011-04-27 15:06 ` Bart Schaefer
2011-04-28 20:19 ` Felipe Contreras
2011-04-29 3:31 ` Bart Schaefer
2011-05-02 18:11 ` Felipe Contreras
2011-05-03 1:42 ` Bart Schaefer
2011-05-03 8:05 ` Felipe Contreras
2011-05-03 14:39 ` Bart Schaefer
2011-05-03 15:04 ` Bart Schaefer
2011-05-03 17:41 ` Felipe Contreras
2011-05-04 0:39 ` Bart Schaefer
2011-05-05 14:39 ` Felipe Contreras
2011-05-05 16:24 ` Bart Schaefer
2011-05-05 16:40 ` Felipe Contreras
2011-05-05 19:38 ` Bart Schaefer
2011-05-05 20:14 ` Felipe Contreras
2011-05-05 21:12 ` Nikolai Weibull
2011-05-03 17:36 ` Felipe Contreras
2011-05-04 0:56 ` Bart Schaefer
2011-05-05 14:48 ` Felipe Contreras
2011-05-05 15:50 ` Bart Schaefer
2011-05-05 15:55 ` Felipe Contreras
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='BANLkTik=Jvvp+af1Zg3487VFQ_7HZyRJ_Q@mail.gmail.com' \
--to=arkanosis@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=zsh-workers@zsh.org \
/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).