git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: 601632@bugs.debian.org
Cc: "Peter van der Does" <peter@avirtualhome.com>,
	"Kevin Ballard" <kevin@sb.org>,
	"Mathias Lafeldt" <misfire@debugon.org>,
	"SZEDER Gábor" <szeder@ira.uka.de>,
	"Brian Gernhardt" <brian@gernhardtsoftware.com>,
	git@vger.kernel.org
Subject: Re: bash 4.0 breaks some completion scripts
Date: Thu, 2 Dec 2010 17:38:48 -0600	[thread overview]
Message-ID: <20101202233848.GA8438@burratino> (raw)
In-Reply-To: <20101027235919.GB30490@burratino>

Jonathan Nieder wrote:

> Bash 4.0 changed the rules for completion word splitting so that
> they are incompatible with 3.x.  I think some Breaks: will be needed
> to ensure smooth upgrades.

Just FYI: Ah, at last some clarity!

>From the bash 3 manual:

 COMP_WORDS
	An array variable (see Arrays below) consisting of the
	individual words in the current command line.  The
	words are split on shell metacharacters as the shell
	parser would separate them.  This variable is
	available only in shell functions invoked by the
	programmable completion facilities (see Programmable
	Completion below).

>From the bash 4 manual:

 COMP_WORDS
	An array variable (see Arrays below) consisting of the
	individual words in the current command line.  The
	line is split into words as readline would split it,
	using COMP_WORDBREAKS as described above.  This
	variable is available only in shell functions invoked
	by the programmable completion facilities (see
	Programmable Completion below).

The workaround used by the bash-completion scripts is to paste words
from COMP_WORDS together (in _get_comp_words_by_ref).

If only the NEWS file had mentioned it. :)  

       reply	other threads:[~2010-12-02 23:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101027235919.GB30490@burratino>
2010-12-02 23:38 ` Jonathan Nieder [this message]
2010-12-03  0:11   ` bash 4.0 breaks some completion scripts SZEDER Gábor

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=20101202233848.GA8438@burratino \
    --to=jrnieder@gmail.com \
    --cc=601632@bugs.debian.org \
    --cc=brian@gernhardtsoftware.com \
    --cc=git@vger.kernel.org \
    --cc=kevin@sb.org \
    --cc=misfire@debugon.org \
    --cc=peter@avirtualhome.com \
    --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).