From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: 4.3.13 changes
Date: Mon, 12 Sep 2011 20:51:48 +0100 [thread overview]
Message-ID: <20110912205148.6d1317d6@pws-pc.ntlworld.com> (raw)
In-Reply-To: <CADdV=Mt0-rH-wkbrHng9GiF+FGa4p9zz1-vdewn=48z1ZA-RmA@mail.gmail.com>
On Fri, 22 Jul 2011 13:13:49 +0200
Nikolai Weibull <now@bitwi.se> wrote:
> Can you please have a look at the '*:: :->file' problem that I’m
> having with _arguments (see _git-add in Completion/Unix/Command/_git)?
> I need to know if this is a problem with _arguments or if I’m doing
> something wrong. The gist of it is that options don’t complete after
> arguments if you use “::” instead of “:”.
I finally looked at this. The documentation says
With two colons before the message, the words special array and the
CURRENT special parameter are modified to refer only to the normal
arguments when the action is executed or evaluated.
I can't see any evidence not being able to complete options thereafter
is deliberate. This is to do with the restrict_range() calls in
ca_set_data(), I think. The :: causes the first argument to be
ca_laststate.argbeg instead of ca_laststate.optbeg, which fits the
descxription; I can't see any other intentional effect. It's possible
there's some miscounting later, or something, but it looks obscure.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2011-09-12 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 11:08 Peter Stephenson
2011-07-22 11:13 ` Nikolai Weibull
2011-09-12 19:51 ` Peter Stephenson [this message]
2011-09-18 11:19 ` Nikolai Weibull
2011-09-25 22:48 ` Bart Schaefer
2011-08-19 20:53 ` İsmail Dönmez
2011-08-19 20:53 ` İsmail Dönmez
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=20110912205148.6d1317d6@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.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).