oh-my-fish: Install fails on macOS

Here’s my versions:

onbjerg@gh0st ~> git --version
git version 2.9.1
onbjerg@gh0st ~> fish --version
fish, version 2.2.0
onbjerg@gh0st ~> uname -a
Darwin gh0st 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

Log:

onbjerg@gh0st ~> curl -L https://github.com/oh-my-fish/oh-my-fish/raw/master/bin/install | fish
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   140  100   140    0     0    203      0 --:--:-- --:--:-- --:--:--   202
100  4693  100  4693    0     0   5323      0 --:--:-- --:--:-- --:--:--  5323
Installing Oh My Fish to /Users/onbjerg/.local/share/omf...
Cloning master from https://github.com/oh-my-fish/oh-my-fish.git...
Existent config.fish found at /Users/onbjerg/.config/fish
↳ Moving to /Users/onbjerg/.config/fish/config.1470592971.copy
Adding startup code to fish config file...
Building Oh My Fish configuration...
Illegal command name '{$OMF_CONFIG,$OMF_PATH}/pkg/*/key_bindings.fish'
~/.local/share/omf/init.fish (line 33):                       {$OMF_CONFIG,$OMF_PATH}/pkg/*/key_bindings.fish \
                                                              ^
from sourcing file ~/.local/share/omf/init.fish
        called on line 10 of file ~/.config/fish/config.fish

from sourcing file ~/.config/fish/config.fish
        called during startup

fish: Unknown command 'omf install'
fish: omf install
      ^
Oh My Fish installation failed.

If you think that it's a bug, please open an
issue with the complete installation log here:

http://github.com/oh-my-fish/oh-my-fish/issues

EDIT Updated to fish 2.3.1 and still no dice. Same error.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments

Actually we’ve had the autocrlf issue before (#217). It was an OS X as well, but that’s a distraction, while the dead giveaway is the ignored little backslash (\) at the end. We’ll have to keep that in mind.

Awesome @onbjerg, thanks for helping us narrowing this issue. Now it will be much easier if someone comes with the same issue again, thank you!! 👍 🎉