Hi,
An older iteration of [2/4] was just reviewed by SZEDER on the list.
[1/4] and [3/4] have been sent out in the past, but haven't been
picked up. [4/4] is new.
Thanks.
Ramkumar Ramachandra (4):
completion: complete rebase --edit-todo
completion: add completer for status
completion: add completer for rev-parse
completion: prefer to use local git-completion.bash
contrib/completion/git-completion.bash | 45 ++++++++++++++++++++++++++++++++++
contrib/completion/git-completion.zsh | 2 +-
2 files changed, 46 insertions(+), 1 deletion(-)
--
1.8.3.1.585.g9832cb9
git-completion.zsh looks in various "default" locations for
git-completion.bash. During development, the location
$(dirname ${funcsourcetrace[1]%:*})/git-completion.bash
is the most obvious and up-to-date version. Push it up on the list of
locations.
Signed-off-by: Ramkumar Ramachandra <redacted>
---
contrib/completion/git-completion.zsh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
In the completion script we support porcelain commands. I'm not sure
about 'git rev-parse', but I think it's more plumbing than porcelain.
However, I think the same about 'git ls-tree' and 'git reflog', too,
yet we have support for them in the completion script.
Either way, why these five options? 'git rev-parse' has a lot more
options than that.
+ return
+ ;;
+ esac
+ __gitcomp_nl "$(__git_refs)"
+}
+
_git_revert ()
{
case "$cur" in
--
1.8.3.1.585.g9832cb9
The code is OK, the rest of the function is pretty straightforward,
but I think this line would warrant a sentence in the log message,
considering that at first you also wondered what '--with-tree=HEAD' is
about.
The code is OK, the rest of the function is pretty straightforward,
but I think this line would warrant a sentence in the log message,
Okay.
Complete untracked pathspecs (--others), and overlay HEAD tree on
index (--with-tree=HEAD) to complete pathspecs that have been removed
from the filesystem + staged in the index.