zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: using the description from _arguments foo:description:->state
Date: Tue, 20 Sep 2011 17:16:33 +0200	[thread overview]
Message-ID: <CAHYJk3RSc0bEApiyP5+=7Sm443iemHwDb4mQ_3OfGj5vR1ivAQ@mail.gmail.com> (raw)
In-Reply-To: <110911111050.ZM11625@torch.brasslantern.com>

On 11 September 2011 20:10, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 11,  5:04pm, Mikael Magnusson wrote:
> }
> }  "($opts)-A[define widget alias]:old widget:->widget :new widget:->widget"
> }
> } Is there any way to get that description from the $state handler and
> } pass it on to compadd?

[partial quote]

> Given the usual state (ahem) of the _arguments code, it's surprisingly
> straightforward to add a parallel array for passing back the description:
>
> However, because callers of _arguments are responsible for declaring
> state as a local, there are a HUGE number of files that would have to
> be updated to also declare state_descr as a local ... UNLESS we were
> willing to declare it local in _main_complete as is done with the
> opt_args variable (which is also supposed to be declared local by all
> callers of _arguments but conspicuously is not by several completers
> including _zle).
>
> Opinions?

Can we add a new option to _configure which enables this, so if you
say _arguments -d you also have to local state_descr. There's a couple
of other variables that work like this already, -n for NORMARG, -C for
curcontext.

-- 
Mikael Magnusson


  reply	other threads:[~2011-09-20 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-11 15:04 Mikael Magnusson
2011-09-11 18:10 ` Bart Schaefer
2011-09-20 15:16   ` Mikael Magnusson [this message]
2011-09-21 11:39     ` Oliver Kiddle
2011-09-21 15:50       ` Bart Schaefer
2011-09-21 17:10         ` Oliver Kiddle
2011-09-22  4:04           ` 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='CAHYJk3RSc0bEApiyP5+=7Sm443iemHwDb4mQ_3OfGj5vR1ivAQ@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=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).