Editor configuration in Git - Step-by-Step Execution

Process Flow - Editor configuration

Start Git Commit

↓

Check for core.editor

↓

Use core.editor

↓

Open editor

↓

User writes commit message

↓

Save and close editor

↓

Git uses message for commit

↓

End

Git uses an editor to write commit messages. It checks if you set an editor, otherwise it uses a default one.

Execution Sample

Git

git config --global core.editor "nano"
git commit

Sets nano as the editor for git commits and then starts a commit which opens nano.

Process Table

Step	Action	Check/Command	Result/State
1	Run 'git config --global core.editor "nano"'	Set editor to nano	core.editor set to nano in global config
2	Run 'git commit'	Git checks core.editor	Finds nano as editor
3	Git opens nano editor	Editor opens	User sees nano with commit message template
4	User writes commit message	User input	Message buffer updated
5	User saves and closes nano	Save and exit	Commit message saved
6	Git reads commit message	Read message file	Commit message ready
7	Git completes commit	Commit created	Commit recorded with user message

💡 Commit message saved and commit completed successfully

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
core.editor	unset	nano	nano	nano	nano	nano	nano	nano
commit_message	empty	empty	empty	empty template	user text	saved text	saved text	saved text

Key Moments - 3 Insights

Why does git open nano instead of vim after setting core.editor?

Because the global config core.editor was set to nano in step 1, git uses that editor as shown in execution_table row 2.

What happens if the user closes the editor without saving?

Git will not have a commit message saved (step 5), so the commit will abort or prompt again, as the message buffer remains empty.

How does git know which editor to open if core.editor is not set?

Git falls back to the system default editor (like vim or vi), as shown in the concept_flow branch where core.editor is not set.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of core.editor after step 1?

A vim

B unset

C nano

D emacs

💡 Hint

Check the 'core.editor' variable in variable_tracker after step 1

At which step does the user input the commit message?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Action' column in execution_table where user writes commit message

If core.editor was not set, what would git do when running 'git commit'?

A Use the system default editor

B Fail with error

C Open nano anyway

D Skip commit message

💡 Hint

Refer to concept_flow where git checks for core.editor or default editor

Concept Snapshot

Git editor configuration:
- Set editor: git config --global core.editor "editor_name"
- Git uses this editor for commit messages
- If unset, uses system default editor
- Editor opens for user to write message
- Save and close to complete commit

Full Transcript

This visual execution shows how git uses an editor for commit messages. First, the user sets the editor with 'git config --global core.editor "nano"'. Then, when running 'git commit', git checks this setting and opens nano. The user writes the commit message, saves, and closes nano. Git reads the message and completes the commit. If no editor is set, git uses the system default editor. Variables like core.editor and commit_message change state through these steps.

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