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; q=dns; s=
	default; b=YaD6oqVgy1hKy+hf/8Xo9+9Ti/jlCR5mXxMzlZTVqjLFBCukRQD0G
	4/tUA09sRGQ+jJaq8v9oryFoMxb+J/btkd+YSsvnp6hFZWawquKQ+81GI1NwRgMw
	XYGdn1CDb5Sn2C6LvUTADLoHZr+FYcHajRksV9lgJQNfSWgNby5vlc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Andrew Schulman <schulman DOT andrew AT epa DOT gov>
Subject: Re: Fish 2.1.0 aborted
Date: Tue, 28 Oct 2014 04:52:49 -0400
Lines: 32
Message-ID: <vjhu4a5grcb45iro78ura9vd6kljhc2jb0@4ax.com>
References: <544F28F8 DOT 2050703 AT cisra DOT canon DOT com DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> Sorry, I tried but I couldn't repeat this crash of fish, when I tried it 
> today for the first time.  But the diagnostic output from fish was 
> reasonable, so it may help.

Thanks for reporting.  

fish 2.1.1 is available in setup, and I recommend that you upgrade.  It has
about a year of bug fixes since 2.1.0, so this problem could be fixed
there.  

If the problem does persist, the best thing to do will be to report it on
the fish-users mailing list.  The fish authors are there and can address it
much more effectively than I can.
 
> BTW, startup of fish took at least 30 seconds before anything started 
> happening.

OK.  This is hard to evaluate on its own.  How does that compare to
starting dash or bash?

My observation is that fish takes about as long to start as bash, with both
shells fully configured with my customizations.  That's about what I'd
expect.  On one of my slower machines, there's a noticeable lag in printing
the prompt, when I do some processing to compute it.

> luke AT CID ~> nWarning: exec_subshell called off of main thread. Break on 
> debug_thread_error to debug.

I see this message a few times a week.  Not sure yet what causes it, but it
seems to be related to autocompletion.

Andrew


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