X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <20100722171413 DOT GA943 AT ns DOT sdsitehosting DOT net> <4C48803D DOT 906 AT cygwin DOT com> <20100722184328 DOT GA3431 AT ns DOT sdsitehosting DOT net> <4C48A0AE DOT 8060607 AT cygwin DOT com> Date: Tue, 27 Jul 2010 18:42:35 +0100 Message-ID: Subject: Re: Cygwin command line takes a long time to start From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 26 July 2010 00:26, David Antliff wrote: > Thanks everyone - using these tips I was able to determine that > bash_completion was actually running twice - once by > /etc/profile.d/bash_completion.sh, and again by my own .bash_profile, > which was modifying the path prior to invoking it so that apps in my > ~/bin were picked up. I don't actually have anything useful in there > any more so it's really just a bunch of old stuff I brought over from > my Linux config. > > I've tidied it up now. I now get the bash prompt after about 5 > seconds, rather than 10. Disabling bash_completion completely gives me > a prompt in less than 1 second, but I do quite like bash_completion so > I'll live with that. FWIW, zsh with fancy completion enabled starts in one to two seconds for me. Not suggesting that switching shell is an easy fix though. Andy -- 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