Editor configuration in Git - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to set Vim as the default Git editor.

Git

git config --global core.editor [1]

Drag options to blanks, or click blank then click option'

Acode

Bnano

Cemacs

Dvim

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nano' or 'emacs' if you want Vim specifically.

Forgetting to use --global to set it for all repositories.

This command sets Vim as the default editor for Git commit messages and other editing tasks.

2fill in blank

medium

Complete the command to set Visual Studio Code as the default Git editor.

Git

git config --global core.editor [1]

Drag options to blanks, or click blank then click option'

Acode --wait

Bvscode

Ccode

Dcode -w

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'code' without '--wait' causes Git to continue before editing is done.

Using 'vscode' which is not a valid command.

The '--wait' option tells Git to wait until the editor window is closed before continuing.

3fill in blank

hard

Fix the error in this command to set Nano as the Git editor.

Git

git config --global core.editor [1]

Drag options to blanks, or click blank then click option'

Anano --wait

Bnano -wait

Cnano -w

Dnano

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--wait' which Nano does not support.

Forgetting to disable line wrapping with '-w'.

The '-w' flag tells Nano to disable wrapping, which is recommended for Git editor usage.

4fill in blank

hard

Fill both blanks to configure Git to use Emacs as the editor with no backup files.

Git

git config --global core.editor "emacs [1] [2]"

Drag options to blanks, or click blank then click option'

A-nw

B-q

C-no-backup

D-no-bak

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent flags like '-no-backup'.

Forgetting to run Emacs in no-window mode.

Using '-nw' runs Emacs in no-window mode, and '-q' disables the startup message, making it cleaner for Git.

5fill in blank

hard

Fill all three blanks to set Sublime Text as the Git editor with wait option.

Git

git config --global core.editor "[1] [2] [3]"

Drag options to blanks, or click blank then click option'

Asubl

B-n

C-w

D--wait

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--wait' instead of '-w' for Sublime Text.

Omitting the '-n' flag causing reuse of existing window.

'subl' is the Sublime Text command, '-n' opens a new window, and '-w' tells Git to wait for the editor to close.

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