From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: zle messes up 'words' variable?
Date: Wed, 27 Apr 2011 08:06:06 -0700 [thread overview]
Message-ID: <110427080606.ZM9595@torch.brasslantern.com> (raw)
In-Reply-To: <BANLkTik3BGrNd389-cDELWwdqR_LZ-qgOA@mail.gmail.com>
On Apr 27, 11:26am, Felipe Contreras wrote:
}
} Strangely enough, if I use the #compdef tag, the code works fine
} (words="foo").
}
} Any ideas?
Hrm. #compdef is equivalent to "compdef -na ..." and causes the
function to be autoloaded at the time it's referenced. I don't know
of any other reason the -na options would change the behavior. Does
the code work fine on repeated attempts or only the first time?
What may be happening is that "sticky emulation" is in effect, so that
when the function is autoloaded in bash compatibility mode, "words"
becomes non-special. If so, I'm not familiar enough with bashcompinit
to say whether that's intentional or an accidental side-effect.
next prev parent reply other threads:[~2011-04-27 15:06 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
2011-04-27 9:11 ` Felipe Contreras
2011-04-27 9:51 ` Felipe Contreras
2011-04-27 15:06 ` Bart Schaefer [this message]
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=110427080606.ZM9595@torch.brasslantern.com \
--to=schaefer@brasslantern.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).