public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kelley Cook <r.kelley.cook@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>,
	Andrew Schulman <schulman.andrew@epa.gov>
Subject: Re: Updated: fish-2.2.0-1 (test release)
Date: Fri, 21 Aug 2015 17:10:00 -0000	[thread overview]
Message-ID: <CAAb7UtBGrChZf+fTN2mT81vGY7m5LU739sEEj5ME1=s6sfinOQ@mail.gmail.com> (raw)
In-Reply-To: <7m8etapaho3t1ve0a5c414g1vof6lnln4c@4ax.com>

On Fri, Aug 21, 2015 at 10:17 AM, Andrew Schulman
<schulman.andrew@epa.gov> wrote:
>
>
> 1. You may see errors when fish starts, saying that "Old versions of fish appear
> to be running."  This is because of architectural changes (removal of fishd)
> from fish 2.1 to 2.2.  If you see this, please try the following things:
>
> * Kill all running instances of fish and, especially, fishd (pkill fish, or
> killall fish).
>
> * Remove all directories /tmp/fishd.* (rm -rf /tmp/fishd.*)
>
> * If necessary, rm ~/.config/fish/fishd.* .  But this probably will remove all
> of your stored universal variables.
>
> Then restart fish.  If the error messages persist, please report that to the
> cygwin list.
>

Andrew,

I followed these instructions and it still told me there were old
version running.

However, the message went away after I also removed a
/tmp/fish.<username> directory [note this was fish not fishd]

Kelley

--
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:[~2015-08-21 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7m8etapaho3t1ve0a5c414g1vof6lnln4c@4ax.com>
2015-08-21 17:10 ` Kelley Cook [this message]
2015-08-22  8:31   ` Andrew Schulman

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='CAAb7UtBGrChZf+fTN2mT81vGY7m5LU739sEEj5ME1=s6sfinOQ@mail.gmail.com' \
    --to=r.kelley.cook@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=schulman.andrew@epa.gov \
    /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).