X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0	tests=AWL,BAYES_00,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4CC308B8.6090102@veritech.com>
Date: Sat, 23 Oct 2010 12:09:28 -0400
From: "Lee D. Rothstein" <l1ee057 AT veritech DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bash Completion Install/Configure ; was: Re: Bash problems, strace, performance, etc.
References: <4CBE119C DOT 9070504 AT veritech DOT com>	<4CBE179C DOT 7020008 AT veritech DOT com>	<4CBFCE23 DOT 3010706 AT laposte DOT net>	<4CC0AF02 DOT 1090600 AT veritech DOT com> <AANLkTinxqkPFWgOQkXBcAyuDK_vbqxxWAfg7g-EiEU7=@mail.gmail.com> <4CC204F7 DOT 1030603 AT cornell DOT edu> <4CC20663 DOT 6080805 AT redhat DOT com>
In-Reply-To: <4CC20663.6080805@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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

  On 10/22/2010 5:47 PM, Eric Blake wrote:
 > On 10/22/2010 03:41 PM, Ken Brown wrote:
 >> On 10/22/2010 12:32 AM, Andy Koppe wrote:
 >>> On 21 October 2010 22:22, Lee D. Rothstein wrote:

The original complaint which is now solved (I think) had nothing
to do with Bash completion. Cyrille brought it up, and it's
become a crimson (not just red ;-)) herring. (I am grateful to
"Ducky" on "NCIS" for explaining that obscure idiom to me. ;-)).

I understood before my posts, during my posts, and after my posts
(;-), that enabling Bash completion requires editing the startup
scripts. The situation, with Bash completion install, as it
exists, is fine, IMHDIO.

I install everything on my system because there are so few things
I don't want, that's its easier to remember to install everything
and then not invoke/configure/load, that which I don't want. My
only complaint would be if the maintainer somehow updated my
customized startup scripts. And, that has/will never likely
happene(d), because Cygwin maintainers are users and aware of the
consequences of such rash actions.  :-|, 8-)

My only vote would be for an option to NOT skip library updates in
'setup.exe', but suggestions about 'setup' without the willingness
and ability to make them one's own self, are usually met with calls
for crucifixion.  Alas, I don't have the ability, and object to the
latter on religious, if not personal grounds. ;-)

Thanks,

Lee

 > Hmm - maybe this is a case of a copy and paste bug on my part.
 > Certainly, before bash-completion 1.0, you had to manually
 > enable things.  But it looks like 1.0 and later (first cygwin
 > build in Apr 2009) inherit the upstream default of automatic
 > enabling.

 > I'll have to revisit that next time I package bash-completion,
 > and either fix the release notes to match reality, or alter the
 > packaging to restore the manual enabling (but note that other
 > distros like Fedora do automatic enabling if you install the
 > package, so that's the direction I'm leaning in).




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