X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=gjnZXxZ0M/2vp+9dEosIjH7GdLRdLL
	GvxFPksWqm3Cr5zQZfRyN9Tgk5XN0LN3tuYU5aJqJseGaXGGJg/8I1NV8qtOBGDF
	NfctQSNTuND2O/vwKwP/vKv8G+BIOb/4UnIKPPN6phFBV022VjgJ2tMQGFLHDMuR
	4b8GUkQJpIIC0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=noxFr1EZSecXA8iAASDkbDHWtbw=; b=fjmF
	BV8LIOiDAtf9bsRgrXm2tAzXAocGfJ3jM6k7lIJzlDD51p21QUQZcoQ7+dh2XJ33
	bDd9kn8jwX3zwrp8kdVH03QCyX9YP3ZF/tZITF134Wx2Xditvbdh5d3zj08x+P4f
	BrFlqDmYyd5xzJzKfOJ2LRN7W4lRSNpgz13kUaQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_FSL_HELO_BARE_IP_2 autolearn=ham version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject: Re: perl -d causes completion to fail
Date: Wed, 22 Oct 2014 10:09:11 -0700
Lines: 73
Message-ID: <m28obo$57h$1@ger.gmane.org>
References: <m1kb7c$rko$1 AT ger DOT gmane DOT org> <20141015184735 DOT GE9828 AT dinwoodie DOT org> <m1mp2b$l79$1 AT ger DOT gmane DOT org> <m1mr9b$gjg$1 AT ger DOT gmane DOT org> <20141020112344 DOT GF9828 AT dinwoodie DOT org> <m23fb0$v3s$1 AT ger DOT gmane DOT org> <54456AFF DOT 3070306 AT cornell DOT edu> <m23tcj$emr$1 AT ger DOT gmane DOT org> <20141022145051 DOT GG9828 AT dinwoodie DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
In-Reply-To: <20141022145051.GG9828@dinwoodie.org>
X-IsSubscribed: yes

On 10/22/2014 7:50 AM, Adam Dinwoodie wrote:

>> I've never installed any Cygwin stuff from anything other than
>> setup.exe.  The Cygwin mirror I typically use is
>> http://mirrors.kernal.org. Oddly enough, looking at it now, I see
>> Current as 2.1-1 and "new" as 1.3-1. Huh? OK... Installing "new"...
>
> Cygwin Ports uses setup-*.exe for installing its packages.  It's also
> currently distributing bash-completion 2.1-1, so I strongly suspect that
> at some point -- intentionally or not -- you installed the Cygwin Ports
> version.

If I did it was totally unintentional especially considering I don't 
know what a Cygwin Ports is though I imagine it about porting open 
source software to Cygwin and perhaps maybe a site. Are you telling me 
that http://mirrors.kernal.org is a "Cygwin Ports" site?

Ah dang! You're right! I recalled that setup asks for a local package 
dir and I typically keep a Cygwin folder with all of the stuff I use 
downloaded in case anybody else wants to use it locally. I recalled how 
it has directories under it with encoded URL names so I decided to check 
my "repo" and lo and behold there's a 
ftp%3a%2f%2fftp.cygwinports.org%2fpub%2fcygwinports%2f directory there. 
I had no idea that this "Ports" URL was different than any other URL in 
that list...

OK so is this bad? Should I remove it? How would I "back this out"?

> Incidentally, almost everything in this mail trail so far could have
> been skipped if you'd included `cygcheck -srv` output in your initial
> email, as we'd have been able to tell straight away that you weren't
> using the official Cygwin version of bash-completion.
>
>> Well now I do have 1.3-1 and I have an /etc/bash_completion.d/perl,
>> but it behaves the same... :-(
>
> The next step I'd suggest is to check if the upstream bash-completion
> package has the behaviour you're looking for.
>
> If upstream does have this behaviour, you can (a) install it yourself,
> separately from the Cygwin install (but be aware the list won't support
> problems you hit unless/until you can identify the Cygwin-distributed
> component that's causing the problem), and/or (b) request the Cygwin
> bash-completion maintainer upgrade to a more recent version.
>
> If upstream doesn't have this behaviour, I can see a bunch of options:
>
> a) Write a plugin yourself to do it.  The obvious place to put this
>     would be ~/.bash_completion, which is automatically included by the
>     bash_completion scripts if it exists.  Optionally submit it upstream
>     then follow all the previous instructions about getting it included
>     in Cygwin.

Wow! I didn't know that bash_completion sourced ~/.bash_completion. 
That's good to know as I have written my own bash_completions - an 
extensive set that covers just about all of the Clearcase commands 
complete with smarts to complete Clearcase objects like labels, branch 
names, etc. Contact me if you want a copy.

> b) Find the mailing list/equivalent for upstream and ask them to add the
>     feature.  See above if they actually do so.
> c) Find a third-party plugin that provides this feature.  Install it
>     manually or ITP it and have it included in Cygwin properly.
> d) Live without it.

Quite honestly option D is the best choice for me at this moment as this 
is the only thing that doesn't complete for me and I'm about to be 
hammered at work and too busy to follow up on this. Maybe later.

Damn good response though! Thanks.
-- 
Andrew DeFaria
http://defaria.com


--
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