Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
If I delete /run/user/1000/fishd.socket and the file put into .config/fish/
The first completion I try (not further completions) after restarting fishd prints this:
I tried looking for a verbosity option, and using strace. It looks like fishd is trying to create a hard link between /tmp (which is an in-memory filesystem) and /run (which is on SDA1). I don't know why it's suddenly trying to do this, it was working fine before. I last updated fish on September 13th. Here's the full strace output: http://sprunge.us/ZTRN
The 2.1.1 changes do attempt to create a hardlink, but failing should not interrupt the operation of fishd. My guess is that you are running Fedora, which has been shipping prerelease patches.
You shouldn't need to start fishd manually - do universal variables work without it?
I've tested the Fedora-shipped version of fish, and yes - this does happen if you run fishd manually. I think we're running into #1084 as fishd tests if the socket is open, connects to it, then quits, and sometimes gets SIGPIPE.
I'd like to take de8bae3 for 2.1.1 as well - do you think that's reasonable?
Making releases is hard.