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.

Practice

1. What does the Git configuration setting core.editor control?

easy

A. The text editor Git uses for commit messages and other editing tasks

B. The default branch name for new repositories

C. The username for Git commits

D. The remote repository URL

Solution

1. Step 1: Understand the purpose of core.editor

   This setting tells Git which text editor to open when you need to write commit messages or other text inputs.

2. Step 2: Identify what core.editor does not control

   It does not affect branch names, usernames, or remote URLs, which are controlled by other settings.

3. Final Answer:

   The text editor Git uses for commit messages and other editing tasks -> Option A

4. Quick Check:

   core.editor = text editor setting [OK]

Hint: core.editor sets your commit message editor [OK]

Common Mistakes:

• Confusing core.editor with branch or user settings
• Thinking it sets remote URLs
• Assuming it changes Git commands behavior

2. Which of the following is the correct command to set Vim as the default editor for Git globally?

easy

A. git config --global core.editor nano

B. git config --global core.editor vim

C. git set core.editor vim

D. git config core.editor --global vim

Solution

1. Step 1: Recall the correct syntax for setting Git config globally

   The correct command uses git config --global core.editor <editor>.

2. Step 2: Identify the correct placement of options and editor name

   git config --global core.editor vim correctly places --global before the key and sets the editor to vim.

3. Final Answer:

   git config --global core.editor vim -> Option B

4. Quick Check:

   Correct syntax: git config --global core.editor editor [OK]

Hint: Use 'git config --global core.editor editorname' [OK]

Common Mistakes:

• Swapping order of --global and key
• Using 'git set' instead of 'git config'
• Placing --global after the key

3. Given the command git config --global core.editor "code --wait", what happens when you run git commit?

medium

A. Git opens VS Code and waits until you close it before completing the commit

B. Git opens VS Code but immediately completes the commit without waiting

C. Git throws an error because of the spaces in the command

D. Git uses the default editor ignoring this setting

Solution

1. Step 1: Understand the meaning of code --wait

   The --wait flag tells VS Code to pause Git until the editor window is closed.

2. Step 2: Predict Git's behavior on commit

   Git will open VS Code and wait for you to finish editing the commit message before proceeding.

3. Final Answer:

   Git opens VS Code and waits until you close it before completing the commit -> Option A

4. Quick Check:

   Editor with --wait pauses Git until done [OK]

Hint: Use --wait flag so Git waits for editor to close [OK]

Common Mistakes:

• Ignoring the --wait flag effect
• Assuming Git commits immediately
• Thinking spaces cause errors without quotes

4. You set your editor with git config --global core.editor "code", but when you run git commit, Git does not wait for VS Code to close and commits immediately. What is the likely problem?

medium

A. VS Code does not support the -w option

B. You need to add a --wait flag for Git to wait

C. The command should be git config core.editor code without quotes

D. Git requires the editor command to block until exit, but VS Code runs in background

Solution

1. Step 1: Understand Git's requirement for editors

   Git expects the editor command to block (wait) until the editor closes to capture the commit message.

2. Step 2: Analyze VS Code behavior

   VS Code runs asynchronously by default and returns control to Git immediately unless --wait is specified.

3. Final Answer:

   Git requires the editor command to block until exit, but VS Code runs in background -> Option D

4. Quick Check:

   Editor must block Git until done [OK]

Hint: Editor must block Git until closed to save commit [OK]

Common Mistakes:

• Assuming code blocks by default
• Removing quotes causing parsing errors
• Expecting Git to add --wait automatically

5. You want to configure Git to use Emacs as your editor, but only for a single repository, not globally. Which command correctly sets this?

hard

A. git config local core.editor emacs

B. git config --global core.editor emacs

C. git config core.editor emacs

D. git config --system core.editor emacs

Solution

1. Step 1: Understand Git config scopes

   Global config applies to all repos, local config applies to current repo only, system config applies to all users on the machine.

2. Step 2: Identify the correct command for local repo setting

   Using git config core.editor emacs without --global or --system sets the editor only for the current repository.

3. Final Answer:

   git config core.editor emacs -> Option C

4. Quick Check:

   Local config = no --global or --system [OK]

Hint: Omit --global to set editor for current repo only [OK]

Common Mistakes:

• Using --global sets editor for all repos
• Using --system requires admin rights
• Using 'local' without the '--' flag