I have a problem setting Sublime Text 2 as the core.editor with git. I've read through every post I could find addressing the problem, but still nothing is working for me. I am running Windows.

By default, git uses the environment's EDITOR variable. On UNIX-like systems (Linux and Mac), that is usually set to vi. You can change it to Sublime Text by setting the core.editor value git config --global core. Editor 'subl -n -w'. When I do a git diff in my branch I see that line endings have the characters ^M: I want to replace these with Unix line endings before committing my changes. I am using Ubuntu 14.04, git and sublime text 3. Thanks for your help. EDIT: I am looking for a way to change line endings in sublime text 3 not using other utilities or commands.

I have done: git config --global core.editor 'C:/Program Files/Sublime Text 2/sublime_text.exe' and tried that with various arguments like -m. When I open my.gitconfig, this is what is in there: [user] name = Spencer Moran email = smoran02@gmail.com [core] editor = 'C:/Program Files/Sublime Text 2/sublime_text.exe' If I go to Git and type: README.markdown --edit the README file opens in Notepad, not Sublime Text.

Does anyone have any idea what I'm doing wrong or how I could fix this? Windows Sublime Text 2 (Build 2181) The latest just added support for the -w (wait) command line argument. The following configuration will allow ST2 to work as your default git editor on Windows. This will allow git to open ST2 for commit messages and such. Git config --global core.editor 'c:/program files/sublime text 2/sublime_text.exe' -w' Sublime Text 3 (Build 3065) (Build 3065) added the subl.exe command line helper.

Use subl.exe -h for the options available to you. I have hot_exit: true and remember_open_files: true set in my Sublime Text user settings. I have found the following to git config to work well for me.

Git config --global core.editor 'c:/program files/sublime text 3/subl.exe' -w' Mac and Linux Set Sublime as your editor for Git by typing the following command in the terminal: git config --global core.editor 'subl -n -w' With this Git config, the new tab is opened in my editor. I edit my commit message, save the tab ( Ctrl+ S) and close it ( Ctrl+ W). Git will wait until the tab is closed to continue its work.

Imran, This is absolutely incorrect. How to set out of office in outlook 2011 for mac mac.

With Sublime Text 2 and the following configuration, if nothing happens when you close the git commit's comment file: git config --global core.editor 'c:/program files/sublime text 2/sublime_text.exe' -w' If the git commit doesn't finish when you close the COMMIT_EDITMSG comment file in Sublime, I've found this is probably because you are running CMD in administrator mode (and have a Sublime Text already opened in non admin mode). I had the same problem and it worked for me when I started my CMD in normal mode. Ps: just wanted to answer to the problem @david pointed out in the accepted answer's comments, but I couldn't post comment since I'm new here. So I've made a new answer, because I think this can be useful to some people encountering the problem. I just successfully made it with the help of PowerShell (command line tools for windows, which is also be use as the default command line on GithubforWindows) Just make a folder 'WindowsPowerShell' on 'C: Users%username% My Documents'.

Then, create a file called 'profile.ps1'. Make sure that you have the correct file extension,.ps1 and not.txt. Inside the profile.ps1, put this line to set an alias command: Set-Alias subl 'c: program files sublime text 2 sublime_text.exe' Make sure the sublime directory on your machine is correct. You can also see the configuration details in.

Now, I can edit files with Sublime Text 2 via PowerShell command just by typing: subl filename Hopefully this is usefull.

Is an amazing piece of software. To start, it is a clean, functional, and fast code editor. Not only does it have incredible built in features (multi-edit and vim mode), but it has support for plugins, snippets, and many other things. I know there have already been many articles like this online, but I am teaching a class on Sublime Text and thought it would be good to have all the information online. In this article, we'll be diving into the best parts of Sublime Text.