public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: Fish 2.1.0 aborted
Date: Tue, 28 Oct 2014 08:53:00 -0000	[thread overview]
Message-ID: <vjhu4a5grcb45iro78ura9vd6kljhc2jb0@4ax.com> (raw)
In-Reply-To: <544F28F8.2050703@cisra.canon.com.au>

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

      reply	other threads:[~2014-10-28  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  5:26 Luke Kendall
2014-10-28  8:53 ` Andrew Schulman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vjhu4a5grcb45iro78ura9vd6kljhc2jb0@4ax.com \
    --to=schulman.andrew@epa.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).