Git - Configuration and Aliases
You set your Git editor with
git config core.editor vim but Git still opens nano. What could be wrong?You set your Git editor with git config core.editor vim but Git still opens nano. What could be wrong?
medium📝 Troubleshoot Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand config scope
Setting core.editor without --global sets it only for the current repository.Step 2: Identify why nano opens instead
If you run Git commands outside that repo, global config applies, which may default to nano.Final Answer:
You need to set the editor globally with --global flag -> Option CQuick Check:
Use --global to set editor for all repos [OK]
Quick Trick: Use --global to set editor for all projects [OK]
Common Mistakes:
- Assuming vim is unsupported
- Not checking if vim is installed
- Thinking Git needs restart
Master "Configuration and Aliases" in Git
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Git Quizzes