

Update : If you use Visual Studio Code as your main editor, the setup is even more simple and this is actually is the more recommended setup now since this post was published (Visual Studio Code can be downloaded from the link at the bottom of this post). You can certainly substitute the path or program name with whatever text editor you have. Sublime Text is used as an example just because it’s available on Windows, OSX, and Linux. From the Explorer, when you right-click (anywhere a file or not) and then select the Browse with Git Extensions, Git Extensions will open in Browse mode for your current project. Now, if you want to see if the text editor is set correctly, just type in this command: git config -global -listĪnd you should see the core.editor value listed to look like this: macOS / Linux git config -global core.editor "subl -n -w" (i.e., "'C:\Program Files\Sublime Text 4\sublime_text.exe' -w" works the same way as in the example above). You can use single quote or double quotes interchangeably as long as they’re consistent You want to enclose the whole path of your editor within the quotes, then wrap the whole argument with the flag with the other. Pay attention to the placement of single quote (‘) and double quotes (“). Windows git config -global core.editor '"C:\Program Files\Sublime Text 4\sublime_text.exe" -w' The -w basically is to tell Git to wait until all operations within the text editor is done before Git can continue to do its thing afterwards.

What you need to do is set the value of core.editor to the program file of your editor and add a flag -w at the end. After installing Git and initially configuring it, you can further configure it to use your favorite text editor as the default.
