From: Clint Adams <clint@zsh.org>
To: Nikolai Weibull <now@bitwi.se>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: _git log arguments
Date: Mon, 1 Oct 2007 09:36:35 -0400 [thread overview]
Message-ID: <20071001133635.GA10543@scowler.net> (raw)
In-Reply-To: <dbfc82860710010016y4770a963k5e8a3c088f8cc7a1@mail.gmail.com>
On Mon, Oct 01, 2007 at 09:16:54AM +0200, Nikolai Weibull wrote:
> Why use "$revision_arguments[@]"? $revision_arguments works just as
> good and you don't need all the quoting and expansion fluff. I see
> this style has been used for $merge_args as well, even though most of
> the file doesn't.
I seem to recall it being necessary for $merge_args, though I don't
recall the specifics.
> > + '*:tree-ish: _alternative c\:\:__git_committishs f\:\:_files' && ret=0
>
> I don't like this at all. Why not simply use __git_cached_files? And
> if we really need __git_committishs, let's at least use a separate
> function for that with proper descriptions and tags.
Your patch reworked against HEAD is below. Now how do we accommodate
the people that want to have a branch name completed after git log?
Index: Completion/Unix/Command/_git
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_git,v
retrieving revision 1.36
diff -u -r1.36 _git
--- Completion/Unix/Command/_git 30 Sep 2007 19:41:57 -0000 1.36
+++ Completion/Unix/Command/_git 1 Oct 2007 13:33:46 -0000
@@ -1705,8 +1705,8 @@
__git_setup_revision_arguments
_arguments -S \
- "$revision_arguments[@]" \
- '*:tree-ish: _alternative c\:\:__git_committishs f\:\:_files' && ret=0
+ $revision_arguments \
+ '*:file:__git_cached_files' && ret=0
}
# TODO: repository needs fixing
next prev parent reply other threads:[~2007-10-01 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 19:40 Clint Adams
2007-10-01 7:16 ` Nikolai Weibull
2007-10-01 13:36 ` Clint Adams [this message]
2007-10-01 13:56 ` Nikolai Weibull
2007-10-01 19:37 ` Clint Adams
2007-10-01 22:02 ` Nikolai Weibull
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=20071001133635.GA10543@scowler.net \
--to=clint@zsh.org \
--cc=now@bitwi.se \
--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).