zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] _git: Add completion for help subcommand
Date: Mon, 30 Aug 2010 23:57:48 -0700	[thread overview]
Message-ID: <100830235750.ZM6368@torch.brasslantern.com> (raw)
In-Reply-To: <AANLkTinuZxQToj3aUQWsJovzwfk2SDJ3mstKJhxZNKWo@mail.gmail.com>

On Aug 30,  8:59pm, Nikolai Weibull wrote:
} Subject: Re: [PATCH] _git: Add completion for help subcommand
}
} > On Aug 26,  9:55am, Nikolai Weibull wrote:
} 
} > } (    --b --c)--a
} > } (--a     --c)--b
} > } (--a --b    )--c
} 
} 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).

Hmm.  I'm not certain, now that you mention it.  The functions that
use the above form are generally some of the earliest completions
that were ever written (or were cribbed from those early ones), so it
may be that at one point in the past it was a problem to exclude the
same option one was defining, e.g., (--a)--a would break.  If that's
not currently the case [I don't know either way] then you're right,
one might as well use the style with the variable.

-- 


  reply	other threads:[~2010-08-31  6:58 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
2010-08-31  6:57           ` Bart Schaefer [this message]
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=100830235750.ZM6368@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).