From: Simon Ruderich <simon@ruderich.org>
To: zsh-workers@sunsite.dk
Subject: Re: [PATCH] git add -p file completion
Date: Wed, 1 Apr 2009 00:27:57 +0200 [thread overview]
Message-ID: <20090331222757.GB14879@ruderich.org> (raw)
In-Reply-To: <dbfc82860903311124lc967575t39bfb7580f47c5e5@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Mar 31, 2009 at 08:24:17PM +0200, Nikolai Weibull wrote:
> On Tue, Mar 31, 2009 at 18:04, Simon Ruderich wrote:
>
>> - - '(-p --patch : -)'{-p,--patch}'[like -i but go directly into patch mode for specified files]' \
>> + '(-p --patch)'{-p,--patch}'[like -i but go directly into patch mode for specified files]' \
>
>> By the way, is the usage of : - documented somewhere in the
>> completion man page? I couldn't find it.
>
> Yes, just search for _arguments and read up on it.
Thanks, found it.
> By the way, -A and -u are mutually exclusive. Care to create a patch
> for that as well?
This should work (I hope), contains the other patch as well:
diff --git a/Completion/Unix/Command/_git b/Completion/Unix/Command/_git
index 8c414b8..534307a 100644
- --- a/Completion/Unix/Command/_git
+++ b/Completion/Unix/Command/_git
@@ -1331,9 +1332,9 @@ _git-add () {
'(-v --verbose)'{-v,--verbose}'[show files as they are added]' \
'(-f --force)'{-f,--force}'[allow adding otherwise ignored files]' \
'(-i --interactive : -)'{-i,--interactive}'[add contents interactively to the index]' \
- - '(-p --patch : -)'{-p,--patch}'[like -i but go directly into patch mode for specified files]' \
- - '(-u --update)'{-u,--update}'[update only files git already knows about]' \
- - '(-A --all)'{-A,--all}'[act as both add . and add -u]' \
+ '(-p --patch)'{-p,--patch}'[like -i but go directly into patch mode for specified files]' \
+ '(-u --update -A --all)'{-u,--update}'[update only files git already knows about]' \
+ '(-A --all -u --update)'{-A,--all}'[act as both add . and add -u]' \
'(-N --intent-to-add)'{-N,--intent-to-add}'[record only that the path will be added later]' \
'--refresh[do not add files, but refresh their stat() info in the index]' \
'--ignore-errors[continue adding if an error occurs]' \
Simon
- --
+ privacy is necessary
+ using http://gnupg.org
+ public key id: 0x6115F804EFB33229
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAknSmO0ACgkQYRX4BO+zMinoDACgyxiYWew4BJnN/b06heEtrcGW
sLEAnR8gqf2wZ2vvnkygfdbKIobL5AR0
=pozu
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-03-31 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 16:04 Simon Ruderich
2009-03-31 18:24 ` Nikolai Weibull
2009-03-31 22:27 ` Simon Ruderich [this message]
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=20090331222757.GB14879@ruderich.org \
--to=simon@ruderich.org \
--cc=zsh-workers@sunsite.dk \
/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).