From: Marc Branchaud <marcnarc@xiplink.com>
To: Peter van der Does <peter@avirtualhome.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Brian Gernhardt" <brian@gernhardtsoftware.com>,
"Kevin Ballard" <kevin@sb.org>,
"Mathias Lafeldt" <misfire@debugon.org>
Subject: Re: [PATCH v3/RFC 1/2] Introduce functions from bash-completion project.
Date: Mon, 01 Nov 2010 09:35:07 -0400 [thread overview]
Message-ID: <4CCEC20B.1020003@xiplink.com> (raw)
In-Reply-To: <1288471350-5392-2-git-send-email-peter@avirtualhome.com>
On 10-10-30 04:42 PM, Peter van der Does wrote:
> The completion script does not work as expected under Bash 4.
> Bash: 3
> output:
> $ git log --pretty=<tab><tab>
> email full medium raw
> format: fuller oneline short
>
> Bash: 4
> output:
> $ git log --pretty=<tab><tab>
> .bash_logout .local/
> .bash_profile Music/
> --More--
>
> With Bash 4 the way word breaking is done in the programmable completion
> code has changed. The documentation at the bash project is not very
> clear what was changed, the only reference found is in the NEWS section:
>
> i. The programmable completion code now uses the same set of characters
> as readline when breaking the command line into a list of words.
>
> The word breaking problem occurs with certain characters, like double
> colon and equal sign.
Nit: "double colon" is "::" -- the name of the character is just "colon".
M.
next prev parent reply other threads:[~2010-11-01 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 20:42 [PATCH v3/RFC 0/2] Make git-completion Bash 4 compatible Peter van der Does
2010-10-30 20:42 ` [PATCH v3/RFC 1/2] Introduce functions from bash-completion project Peter van der Does
2010-11-01 13:35 ` Marc Branchaud [this message]
2010-10-30 20:42 ` [PATCH v3/RFC 2/2] Use the new functions to get the current cword Peter van der Does
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=4CCEC20B.1020003@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=kevin@sb.org \
--cc=misfire@debugon.org \
--cc=peter@avirtualhome.com \
--cc=spearce@spearce.org \
--cc=szeder@ira.uka.de \
/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).