I have installed my sublime text editor in d drive some days ago and i have customized it. and then i have create .bashrc file in users/my-name directory. then i added:
alias subl = 'the directory i have copied from the app-properties'
but it doesn't work..
when i type
subl .
it shows me,
$ subl .
bash: $: command not found
How can I open sublime text editor in git bash.
enter image description here
Let's say you installed sublime in folder d:\Sublime Text 3.
In this way you need set correct path for alias in .bashrc located in directory users/my-name. Please, take note that folder's name can have backspaces.
alias subl="/d/Sublime\ Text\ 3/sublime_text.exe"
To apply changes run commands in git bash:
cd ~
source .bashrc
Then you can run sublime with command:
subl .
This is driving me crazy. I'm running OSX and until today I had Sublime Text 2 installed. After installing Sublime Text 3, when I enter the 'subl' command the terminal logs:
Unable to find application named 'Sublime Text 2'
I've tried everything. I've tried
$ rm ~/bin/subl
Then
$ ln -s /Applications/Sublime\ Text\ 3.app/Contents/SharedSupport/bin/subl ~/bin/subl
I've also tried going in to usr directly and removing the subl command. When I do this, the subl command will sometimes work while I remain in one directory, but once I switch directories it goes back to giving me the message
Unable to find application named 'Sublime Text 2'
With Sublime Text 2 I had subl entered as an alias. I also tried going in and unaliasing subl like this:
unalias subl
And I've tried re-creating the alias using
/Applications/Sublime\ Text\ 3.app/Contents/SharedSupport/bin/subl
Again, this will work for a while, but once I change directories it stops working.
Any advice on what to try next? I'm at a loss. I can't understand why it works for a while, then stops working.
Check your .bashrc file, and .bash_profile and see if it's aliased in there. Both of these are in your home directory ~.
nano ~/.bashrc
nano ~/.bash_profile
No need to sudo as you own these documents.
Before today I had Sublime 2 and 3 on my computer. When I ran the subl command in the terminal it would always open Sublime 2, which I never use anymore. Therefore I got rid of Sublime 2. Now my subl command does not work at all. All I get is subl command not found.
I understand that I have to put a subl binary file into my bin folder. I was just wondering what might be the best way to go about doing that. Any insight on this particular instance would help.
Thanks in advance,
According to their website:
ln -s "/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" ~/bin/subl
(The command is almost identical to the one for version 2.)
If you have a fresh install of OS X, this will probably fail for you. First, create a ~/bin directory under your home and add it to your path. This will vary by your shell, but if you use bash..
mkdir ~/bin
echo "export PATH=$PATH:~/bin" >> ~/.bash_profile
source ~/.bash_profile
Then you should be able to run the ln command and subl to your hearts content.
As a side note, a simplified version of this can be accomplished with the open command for any app. Try open -a TextEdit hello.txt for similar effect. I've aliased this for a hex editor that didn't offer a CLI launcher like subl.
Try this: (it worked for me)
alias subl="'/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl'"
alias nano="subl"
export EDITOR="subl"
Shortly after I posted this question I found the answer. The issue was that because the subl file in my bin or binary folder was tied to Sublime 2, when I uninstalled Sublime 2 it also uninstalled that binary.
All I did was copy the subl file from Sublime 3 into the bin or binary folder. I did have use the terminal in order to get down to the bin folder. Once I opened both folders with the terminal I just copied the subl binary from Sublime 3 to my binary folder.
I have Sublime Text 2 installed on a Mac, and have made a link on the command line as described in the docs.
When opening files from the terminal, as in:
$ subl foo.txt
A Sublime Text window will open, but inside that window foo.txt will only open about one out of every three times or so. I've tried moving the link to a different folder in the path, creating it with sudo, etc., but no luck so far.
Any idea how to fix this?
Had the same problem for a while now. Add the following line to your .bash_profile:
alias subl='subl && sleep 0.1 && subl'
Now you can use subl filename_to_edit to open it.
If you are not sure if you configured subl command correctly, do the following. Run the first command for ST3 or the second for ST2:
ln -s "/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" ~/bin/subl
ln -s "/Applications/Sublime Text 2.app/Contents/SharedSupport/bin/subl" ~/bin/subl
Make sure that ~/bin is in your $PATH. Then do the first step with .bash_profile.
Finally works as it should! Credit goes to these guys and chrisf for improvement.
I remember running into problems with subl before. And had to come up with a function to see if Sublime is running, if not launch it, see if it loaded. Then use "rmate" bash script and the associated "rsub" Sublime Text Package plugin to load in the specified file. However you should be able to use the OSX open command should work for what you need. I would also give the latest Sublime Text 3 Beta a try.
I am a Mac-newbie (Mountain Lion) and try to set up the "subl"-command for the terminal, like described here:
The first task is to make a symlink to subl. Assuming you've placed
Sublime Text 2 in the Applications folder, and that you have a ~/bin
directory in your path, you can run:
ln -s "/Applications/Sublime Text
2.app/Contents/SharedSupport/bin/subl" ~/bin/subl
But it doesn't work. I have now a folder /bin/ under my user and this folder including a alias. But when I tip in subl --help inside the terminal, I get the error -bash: subl: command not found
Can someone helps me out?
KR & thx, Fabian
Change directories to:
/usr/local/bin
then run this instead:
ln -s "/Applications/Sublime Text 2.app/Contents/SharedSupport/bin/subl" subl
I have found the solution now - there was a problem with RVM. The solution is to enter the command
ln -s "/Applications/Sublime Text 2.app/Contents/SharedSupport/bin/subl" ~/.rvm/bin/subl
into the terminal.
That happened to me with Sublime Text 3.
This symlink works for me, only I needed was to change the symlink destination to /usr/local/bin/subl
ln -s "/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" /usr/local/bin/subl
Solution source Paul Byrne answer here
Using Homebrew to install Sublime usually creates the correct symlinks automatically.
brew install Caskroom/cask/sublime-text
Subl can then be accessed like:
# Open Sublime at current directory
subl .
The solution chosen for this question is to put the subl symlink in the ~/.rvm/bin folder which is definitely not a generic solution as this directory is part of a program he has installed.
Although any directory in the path will work, the most common solution is to create a bin directory in the home folder, set it in the path by putting export PATH=$PATH:~/bin in .bash_profile and then running the link command as shown in the original question with this new path.
In the past it was common to put the subl symlink in /usr/local/bin but this directory no longer exists in OSX as of version 10.2 and the /usr/local directory is no longer in the default path.
SOLVED for MAC OSX Mavericks!
I found this answer on this GitHubGist:
https://gist.github.com/artero/1236170
Launch Sublime Text 2 from the Mac OS X Terminal
ln -s /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl /usr/local/bin/sublime
This is the part that I found clarified what many StackOverflow responses have only hinted at, but not explicitly explained:
Now let's do a check to see if everything will run smoothly. Enter this:
open ~/.bash_profile
(In some cases the profile file is named ~/.profile)
You should see at the top of the file a line that starts with: export PATH=
This contains all the directories that will be looked into for executable binaries when you type a command in Terminal. Since we create a symlink to subl called sublime in the /usr/local/bin directory let's check if this directory is listed on that same line.
If it is, perfect. Let's keep going. If not, simply add it like this and save the file:
export PATH=/usr/local/bin:(...)
Note: The '(...)' in this example represents other folders that would be listed on the same line and separated by a colon.
If you don't already have a PATH set in your bash_profile you can type:
export PATH=/usr/local/bin:$PATH
If you had to add /usr/local/bin to your PATH, run the following command before continuing:
source ~/.bash_profile
This will reload your .bash_profile with the newly added directory.
Testing
Open a Terminal window and run:
sublime filename (replace "filename" by an actual file name)
Hope that helps clarify for others as well. Currently (FALL 2014) using Mac OSX Mavericks. Cheers
If you just want the command to open files using sublime text, and you're not bothered to use it as your default editor for all commands, why not just add an alias to your ~/.bash-profile ?
alias subl="open -a 'Sublime Text'"
That will work for opening files and directories
Had the same problem on a MAC with OSX Yosemite 10.10.5, and sublime text 3 Build 3083!
Configuring git to work with the above requirements worked perfectly using:
git config --global core.editor "/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl -n -w"
And test if it worked with:
git config -e
It works on Mac OSX 10.8.2, echo $PATH shows subl symlink correctly linked as described in this post. The other suggestions on Sublime Text 2 page seem not work with new Macs
I discovered that there was an alias for subl. Type alias to see all defined aliases. Find the source and comment it out, or use unalias subl to unset.
For .bashrc or .zshrc
alias subl="open . -a /Applications/Sublime\ Text.app"
Catalina's auto-sandboxing seems to broke the subl command.
Use the following alias as an alternative
alias subl="open $1 -b com.sublimetext.3"
After $ subl . did not work for me,
I tried $ bundle exec subl . and it worked.
Solution: type $ bundle exec subl . and it should work. (Obviously, omitting the $)