From: Nikolai Weibull <now@bitwi.se>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] _git: Add completion for help subcommand
Date: Mon, 30 Aug 2010 20:59:09 +0200 [thread overview]
Message-ID: <AANLkTinuZxQToj3aUQWsJovzwfk2SDJ3mstKJhxZNKWo@mail.gmail.com> (raw)
In-Reply-To: <100830094359.ZM7722@torch.brasslantern.com>
On Mon, Aug 30, 2010 at 18:43, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Aug 26, 9:55am, Nikolai Weibull wrote:
> } Perhaps. The common pattern I saw when I began writing completion
> } functions was
> }
> } ( --b --c)--a
> } (--a --c)--b
> } (--a --b )--c
> Nikolai, I think you're missing the point of the abc example you quoted.
>
> In that example, every set inside the parens is different, and the writer
> of the function chose to lay them out so that it was obvious where the
> differences were.
That had not alluded me. What I never “understood” was why the
standard form wasn’t to use a variable in this case. I mean, the
difference is that you exclude the current option, which is of course
excluded by itself (unless its defined as being able to appear many
times).
next prev parent reply other threads:[~2010-08-30 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 12:21 Aaron Schrab
2010-08-25 22:16 ` Nikolai Weibull
2010-08-26 3:29 ` Benjamin R. Haskell
2010-08-26 7:55 ` Nikolai Weibull
2010-08-30 16:43 ` Bart Schaefer
2010-08-30 18:59 ` Nikolai Weibull [this message]
2010-08-31 6:57 ` Bart Schaefer
2010-08-27 0:20 ` Aaron Schrab
2010-08-27 8:29 ` Nikolai Weibull
2010-08-27 23:18 ` Aaron Schrab
2010-08-27 23:43 ` Nikolai Weibull
2010-08-28 0:51 ` Aaron Schrab
2010-08-28 7:54 ` Nikolai Weibull
2010-08-28 14:16 ` Aaron Schrab
2010-08-28 14:24 ` Nikolai Weibull
2010-12-02 0:44 ` Aaron Schrab
2010-12-04 18:10 ` Wayne Davison
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=AANLkTinuZxQToj3aUQWsJovzwfk2SDJ3mstKJhxZNKWo@mail.gmail.com \
--to=now@bitwi.se \
--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).