I have just upgraded to OS X El Capitan and subl .
command stopped working with the zsh: command not found: subl
error message.
I have run the following command as suggested in other posts:
sudo ln -s /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl
result:
ln: /usr/local/bin/subl: File exists
in the ".bash_profile" as well as ".zsh_profile" I have the following lines saved:
export PATH=/bin:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:$PATH export EDITOR='subl -w'
Also tried:
sudo ln -s /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl /usr/bin/subl
result:
ln: /usr/bin/subl: Operation not permitted
Update: it seemed to work after running the following command:
alias subl="'/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl'"
but as soon as I restart the terminal, subl .
command stops working.
Update2: after pasting the following line: alias subl="'/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl'"
in the subl ~/.zshrc
, subl .
command works even after restarting the terminal, but terminal seems to work slower than normal, and when you open relatively small folders with subl .
command, at times it's taking ages to show the files...
Final Update: After running sudo rm /usr/local/bin/subl
followed by sudo ln -s /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl
everything works perfectly, thanks to @chris.
Sublime Text includes a command-line helper called subl . Using the command-line helper, you can open files and folders and perform other actions from the command line. Before using subl , make sure it is on your PATH . To put subl on your PATH , you may need to add directories to PATH or use symbolic links.
First, navigate to a small folder in Terminal that you want ST to open and enter the following command: /Applications/Sublime\ Text. app/Contents/SharedSupport/bin/subl . NOTE: You may need to replace Sublime\ Text.
In El Capitan, you are not allowed to write to /usr/bin
, but writing to /usr/local/bin
is ok. By default, /usr/local/bin
should also be in your path variable.
Had the same issue. Deleting and recreating the symlink has fixed the problem. Perhaps the current symlink is pointing to the wrong location after the upgrade.
sudo rm /usr/local/bin/subl sudo ln -s /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl
Or Sublime Text 2 (from – @simen comment):
sudo rm /usr/local/bin/subl sudo ln -s /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With