Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3C20D41A.3010203@ece.gatech.edu> Date: Wed, 19 Dec 2001 12:53:30 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin-apps AT cygwin DOT com Subject: Re: bash completion (was: RE: Units) References: <3C20BA86 DOT 6000001 AT ece DOT gatech DOT edu> <20011219161644 DOT GB23322 AT redhat DOT com> <3C20CABF DOT EC49754B AT etr-usa DOT com> <20011219172057 DOT GA24344 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > That's where I would be leaning, too. I think it makes sense to include > the completions in bash. Or maybe in shellutils? > > The only problem with this that I can see is that they'll be more "hidden" > there. If they are a separate setup.exe package then it is more likely > that someone will notice them and say "Hey, cool!" and install them. > > If they just slide in with a bash installation then, unless we make them > the default, it's more likely that people won't know what they have unless > they're reminded about it on the mailing list (or whereever). > > Hmm. Maybe I just convinced myself that they belong as a separate package. How about this: John, why don't you create a "bashutils" package, to serve as a collection of (moderately) useful bash scripts and settings. For now, it could contain only bashcompletion, but later you could add -- oh, bashprompt, or something... I'm thinking something like my cygutils package, which is just a grab bag of very simple (single-source-file) utilities. (FYI, you can find bashprompt here... http://www.neuro.gatech.edu/users/cwilson/cygutils/unversioned/bashprompt/ the official site is completely flaky, so I mirrored it) --Chuck