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: Sun, 13 Mar 2016 21:58:00 -0000	[thread overview]
Message-ID: <56E5E2A0.3060209@cornell.edu> (raw)
In-Reply-To: <87r3fee0kr.fsf@Rainer.invalid>

On 3/13/2016 1:42 PM, Achim Gratz wrote:
> Ken Brown writes:
>> [Achim, /etc/defaults/etc/skel/.bashrc has some outdated comments
>> referring to /etc/bash_completion.]
>
> I need further discussion and preferrably a patch.  Since I don't use
> bash, I don't know anything about how its completion mechanism works and
> reading the man page makes me none the wiser.

I'm not an expert on bash-completion either, but here are my thoughts on 
what's in .bashrc now.  Someone who knows more should comment further.

> # Uncomment to turn on programmable completion enhancements.
> # Any completions you add in ~/.bash_completion are sourced last.
> # [[ -f /etc/bash_completion ]] && . /etc/bash_completion

This is obsolete because (a) /etc/bash_completion has been replaced by 
/usr/share/bash-completion/bash_completion and (b) the latter is already 
sourced by /etc/profile.d/bash_completion.sh.

> # COMP_CVS_REMOTE=1

This is probably OK.

> # COMP_CONFIGURE_HINTS=1

This is probably OK.

> # COMP_TAR_INTERNAL_PATHS=1

I don't think this will have any effect unless it's set *before* 
/usr/share/bash-completion/bash_completion is sourced; so it doesn't 
belong in .bashrc now that /usr/share/bash-completion/bash_completion is 
sourced by /etc/profile.d/bash_completion.sh.

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-03-13 21:58 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
2016-03-13 17:43   ` Achim Gratz
2016-03-13 21:58     ` Ken Brown [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=56E5E2A0.3060209@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).