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.