Editor configuration in Git - Commands & Configuration

Introduction

Sometimes when you write commit messages or edit files in Git, you want to use your favorite text editor. Git lets you set which editor to use so you can work comfortably and efficiently.

When you want to write commit messages in an editor you know well instead of the default one.

When you need to edit Git configuration files or rebase instructions and want a familiar editor.

When you work on different machines and want to keep the same editor experience everywhere.

When you want to avoid confusion by setting a clear editor for all Git commands that open an editor.

When you want to use a graphical editor instead of a command-line one for easier editing.

Commands

This command sets the default editor for Git to 'nano' for all your projects on this computer. Nano is a simple text editor that runs in the terminal.

Terminal

git config --global core.editor nano

Expected Output

No output (command runs silently)

→

--global - Sets the editor for all Git projects for the current user.

This sets Visual Studio Code as the Git editor. The --wait flag tells Git to wait until you close the editor before continuing.

Terminal

git config --global core.editor "code --wait"

Expected Output

No output (command runs silently)

→

--global - Applies the setting globally for the user.

This command shows all Git settings currently active, including the editor you just set. It helps you verify your configuration.

Terminal

git config --list

Expected Output

core.editor=code --wait

user.name=Your Name

user.email=[e-mail]

Starts a commit. Git will open the editor you set so you can write your commit message.

Terminal

git commit

Expected Output

On branch main



No changes added to commit (use "git add" and/or "git commit -a")

Key Concept

If you remember nothing else from this pattern, remember: setting core.editor lets you choose the text editor Git uses for commit messages and other edits.

Common Mistakes

Not using quotes around editor commands with spaces or flags.

Git will misinterpret the command and fail to open the editor correctly.

Always put the editor command in quotes if it includes spaces or flags, like "code --wait".

Setting the editor without the --global flag when you want it for all projects.

The editor will only be set for the current repository, causing confusion on other projects.

Use --global to set the editor for all repositories for your user.

Setting an editor that is not installed or not in the system PATH.

Git will fail to open the editor and block commit or other operations.

Make sure the editor is installed and accessible from the command line before setting it.

Summary

Use 'git config --global core.editor <editor>' to set your preferred editor for Git.

Verify your editor setting with 'git config --list'.

When you run 'git commit', Git opens the editor you set for writing commit messages.