public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: bash completion after equals sign does not work after upgrading to bash_completion 2.1-2
Date: Wed, 24 Feb 2016 16:50:00 -0000	[thread overview]
Message-ID: <56CDDFE7.8020109@cornell.edu> (raw)
In-Reply-To: <56CD6CC6.2000801@le-tex.de>

On 2/24/2016 3:41 AM, Imsieke, Gerrit, le-tex wrote:
> It still works with bash_completion 1.3-1
>
> COMP_WORDBREAKS is the default “ "'><=;|&(:” (the string within “”).
>
> Removing everything in /etc/bash_completion.d did not help
>
> Compared to bash_completion 1.3-1, there is almost nothing in
> /etc/bash_completion.d anyway, and there is no /etc/bash_completion file
> any more.

Right.  bash-completion now uses /usr/share/bash-completion, as you can 
see from

   https://cygwin.com/packages/x86_64/bash-completion/bash-completion-2.1-2

> Moving away my .bashrc (that contains only 'complete -o default make'
> wrt completion and that is symlinked to .bash_profile for some arcane
> reason) didn’t help, either.
>
> The only thing that worked so far (except reverting to bash_completion
> 1.3-1) is to use bash --norc.

That's a pretty clear indication that the problem is caused by something 
in your bash startup files.  And the symlink you mentioned could easily 
be confusing the issue.  Have you tried reverting to the default startup 
files (in /etc/defaults/etc/skel)?

[Achim, /etc/defaults/etc/skel/.bashrc has some outdated comments 
referring to /etc/bash_completion.]

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-02-24 16:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  8:41 Imsieke, Gerrit, le-tex
2016-02-24 16:50 ` Ken Brown [this message]
2016-03-13 17:43   ` Achim Gratz
2016-03-13 21:58     ` Ken Brown

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=56CDDFE7.8020109@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).