From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] bash completion: Fix the . -> .. revision range completion
Date: Mon, 14 Jul 2008 01:07:24 +0200 [thread overview]
Message-ID: <20080713230724.GJ10151@machine.or.cz> (raw)
In-Reply-To: <7vskudpiqq.fsf@gitster.siamese.dyndns.org>
On Sun, Jul 13, 2008 at 02:38:37PM -0700, Junio C Hamano wrote:
> By the way, the above command line is another "dot" related frustration I
> always have. If you try:
>
> git log v1.5.6.<TAB>
>
> the completion code adds a dot unconditionally when I want to choose from
> the list of v1.5.6.X tags. Of course, I can work this around by dropping
> the last dot before asking for completion, so it is not really a very big
> deal, but I mention it here because this annoyance is exactly in the same
> league as your "git-submodule.<TAB>" example.
Actually, my original solution to this problem was simply to remove the
. -> .. completion altogether. Maybe this would still be the best course
of action? I don't think the . -> .. is actually very useful for anyone,
since you might as well just hit the dot another time instead of a tab.
> > contrib/completion/git-completion.bash | 7 ++++++-
> > 1 files changed, 6 insertions(+), 1 deletions(-)
> >
> > diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> > index 61581fe..fe24b8c 100755
> > --- a/contrib/completion/git-completion.bash
> > +++ b/contrib/completion/git-completion.bash
> > @@ -325,7 +325,12 @@ __git_complete_revlist ()
> > __gitcomp "$(__git_refs)" "$pfx" "$cur"
> > ;;
> > *.)
> > - __gitcomp "$cur."
> > + if ls "$cur"* >/dev/null 2>&1; then
>
> There is a slight Yuck factor for using "ls" here but I do not think of a
> better alternative offhand.
I have thought about this hard for some time, but couldn't come up with
anything better than this or
(shopt -s nullglob; completion=("$cur"*); [ -n "$completion" ])
which looks quite awful (and can waste a lot of memory in case of some
really insane completion).
--
Petr "Pasky" Baudis
GNU, n. An animal of South Africa, which in its domesticated state
resembles a horse, a buffalo and a stag. In its wild condition it is
something like a thunderbolt, an earthquake and a cyclone. -- A. Pierce
next prev parent reply other threads:[~2008-07-13 23:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 11:19 [PATCH] bash completion: Fix the . -> .. revision range completion Petr Baudis
2008-07-13 12:11 ` Jakub Narebski
2008-07-13 21:38 ` Junio C Hamano
2008-07-13 22:06 ` Shawn O. Pearce
2008-07-13 23:07 ` Petr Baudis [this message]
2008-07-13 23:25 ` Junio C Hamano
2008-07-13 23:52 ` Linus Torvalds
2008-07-14 0:00 ` Shawn O. Pearce
2008-07-14 5:38 ` Linus Torvalds
2008-07-14 5:57 ` Shawn O. Pearce
2008-07-14 6:27 ` Shawn O. Pearce
2008-07-14 6:47 ` Björn Steinbrink
2008-07-14 6:50 ` Björn Steinbrink
2008-07-14 12:39 ` Andreas Ericsson
2008-07-14 14:51 ` Linus Torvalds
2008-07-14 14:50 ` Linus Torvalds
2008-07-15 4:25 ` Shawn O. Pearce
2008-07-15 8:05 ` Andreas Ericsson
2008-07-15 8:10 ` Andreas Ericsson
2008-07-15 8:17 ` Andreas Ericsson
2008-07-15 23:38 ` Shawn O. Pearce
2008-07-16 7:20 ` Andreas Ericsson
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=20080713230724.GJ10151@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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.
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).