X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 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: <AANLkTilosuPOUqyD22QXA7dMWqsDwyh3Qw6jLF8z3U6z@mail.gmail.com>
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>	<AANLkTimMoOsJxpOrcfpxiun8zAuDbhQ83_K_R_deD4lz AT mail DOT gmail DOT com>	<AANLkTilosuPOUqyD22QXA7dMWqsDwyh3Qw6jLF8z3U6z AT mail DOT gmail DOT com>
Date: Mon, 26 Jul 2010 11:26:35 +1200
Message-ID: <AANLkTi=RZ7siJGD9_CXN+4Tx7Nfi7FiOCqQpz+hxtB=E@mail.gmail.com>
Subject: Re: Cygwin command line takes a long time to start
From: David Antliff <david DOT antliff AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 Mon, Jul 26, 2010 at 08:12, Csaba Raduly wrote:
> On Fri, Jul 23, 2010 at 3:53 AM, David Antliff =A0wrote:
>> How would one go about debugging the bash or mintty startup before
>> .bash_profile is read?
>
> Duplicate your shortcut which launches bash and add -x to the bash
> options (which should include -l a.k.a. --login)

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.

-- David.

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