From: Michael J Gruber <git@drmicha•warpmail.net>
To: Stephen Boyd <bebarino@gmail•com>
Cc: git@vger•kernel.org, "Shawn O. Pearce" <spearce@spearce•org>
Subject: Re: bash completion on 4.0 broken?
Date: Tue, 17 Nov 2009 10:54:50 +0100 [thread overview]
Message-ID: <4B0272EA.5020708@drmicha.warpmail.net> (raw)
In-Reply-To: <4B0246C7.6020401@gmail.com>
Stephen Boyd venit, vidit, dixit 17.11.2009 07:46:
> When I try
>
> git show --pretty=<TAB><TAB>
>
> I get a list of filenames and not the list of pretty formats.
>
> I've debugged a little and see that the cur variable in _git_show () is
> set to '=' when it should be '--pretty='. So it looks like something is
> causing the command line to be split weirdly. Looking at the bash
> NEWS[1] for 4.0 I see
>
> i. The programmable completion code now uses the same set of characters as
> readline when breaking the command line into a list of words.
>
>
> which causes me to believe this is why it's broken now. I've tried
> removing '=' from COMP_WORDBREAKS and that shows the list of formats
> correctly, but then causes the entire '--pretty=' to be replaced with
> the selected format.
>
> Anyone else seeing the same problem or is my system just b0rked?
>
> $ bash --version
> GNU bash, version 4.0.35(2)-release (x86_64-pc-linux-gnu)
>
> References:
> [1] http://tiswww.case.edu/php/chet/bash/NEWS
Ouch, just when I decided to use completion rather than a bunch of
aliases it stops working. B0rked here 0ls0 on Fedora 12 (with git.git's
next):
GNU bash, Version 4.0.33(1)-release (x86_64-redhat-linux-gnu)
Command name completion and prompt magic do work.
Michael
prev parent reply other threads:[~2009-11-17 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 6:46 bash completion on 4.0 broken? Stephen Boyd
2009-11-17 9:54 ` Michael J Gruber [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=4B0272EA.5020708@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=bebarino@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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