Fix fish shell support on Ubuntu about fzf HOT 12 CLOSED

Hmm, even a very simple ls | fzf doesn't work reliably on fish on Ubuntu 14.

jg@jg-VirtualBox ~> ls | fzf
  # returns immediately
jg@jg-VirtualBox ~> fg
Send job 2, “/usr/bin/ruby --disable-gems /home/jg/.fzf/fzf $argv” to foreground
/home/jg/.fzf/fzf:791:in `getc': Input/output error (Errno::EIO)
    from /home/jg/.fzf/fzf:791:in `get_input'
    from /home/jg/.fzf/fzf:995:in `start_loop'
    from /home/jg/.fzf/fzf:232:in `start'
    from /home/jg/.fzf/fzf:1194:in `<main>'

from fzf.

I am also having this issue...

from fzf.

Yup, It seems to be caused by a bug or limitation of fish on Linux, unlike ls | fzf, ls | ruby ~/.fzf/fzf works fine. I'm looking for a workaround.

from fzf.

I'm working on making fzf_key_bindings.fish suck less for my dotfiles, (no offense, it's just not good fish 😝) and you're welcome to my changes when I finish.

Also, seems to be working for me when I set TMPDIR. I fix this in my changes, among other issues.

The changed code will be in neersighted/dotfiles.

from fzf.

Sounds great, actually I was secretly hoping for some help :)
It would be even better if TMPDIR is not required all. Please let me know of the progress, thanks!

from fzf.

Does fzf not block in pipes? I seem to be having some trouble with a cd from stdin function, debugging shows that the function is being called before fzf writes to stdout.

from fzf.

I think it's related to this issue: see http://stackoverflow.com/questions/22729298/fish-command-substitution-issue-with-interactive-command

from fzf.

Done! See the refactored code at https://github.com/neersighted/dotfiles/blob/master/config/fish/functions/fzf_key_bindings.fish

from fzf.

Awesome! I'll test it tonight. You interested in sending a pull request?

And, have you found a way to circumvent the aforementioned problem (#60 (comment))? It happens on Ubuntu, but not on OSX.

from fzf.

I can pull it out into a pull request or you can just copy the file from my repo. It seems to fix this issue for me.

from fzf.

Either way is fine for me. Just felt like I should ask you first :)

from fzf.

Ah, my ls is long by default. If I define fzf as a function and pipe dir, or command ls into it, it hangs. However, I think this is a fzf issue with one line of input, as the output of ls/dir is only one line long and space delimited. I do not have the same issue with find.

from fzf.