Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

StackOverflow Point

StackOverflow Point Navigation

  • Web Stories
  • Badges
  • Tags
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Web Stories
  • Badges
  • Tags
Home/ Questions/Q 217993
Next
Alex Hales
  • 0
Alex HalesTeacher
Asked: July 14, 20222022-07-14T08:33:09+00:00 2022-07-14T08:33:09+00:00In: Git, git-commit, git-merge, Macos

macos – Please enter a commit message to explain why this merge is necessary, especially if it merges an updated upstream into a topic branch

  • 0

[ad_1]

The fix is not to memorize cryptic commands, like in the accepted answer, but configuring Git to use an editor that you like and understand!

The underlying problem is that Git by default uses an editor that is too unintuitive to use for most people: Vim. This is because Vim is present everywhere, not because it is user friendly 😄 Now, don’t get me wrong, I ❤️ Vim, and while you could set some time aside to learn Vim and try to understand why some people think Vim is the greatest editor in existence, there is a quicker way of fixing this problem 🙂

It’s really as simple as configuring either of these options

  1. the git config setting core.editor (per project, or globally)
  2. the VISUAL or EDITOR environment variable (this works for other programs as well). Typically stuffing export VISUAL="vscode --wait" into your .bashrc or similar config.

I’ll cover the first option for a couple of popular editors, but GitHub has an excellent guide on this for many editors as well.

🔥 To use Atom

Straight from its docs, enter this in a terminal:

git config --global core.editor "atom --wait"

Git normally wait for the editor command to finish before progressing, but since Atom forks to a background process immediately, this won’t work, unless you give it the --wait option. This makes it stay as a foreground process, just as we want.

🦄 To use Sublime Text

For the same reasons as in the Atom case, you need a special flag to signal to the process that it shouldn’t fork to the background:

git config --global core.editor "subl -n -w"

🤓 To use Visual Studio Code

git config --global core.editor "code --wait"

[ad_2]

  • 0 0 Answers
  • 5 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report
Leave an answer

Leave an answer
Cancel reply

Browse

Sidebar

Ask A Question

Related Questions

  • xcode - Can you build dynamic libraries for iOS and ...

    • 0 Answers
  • bash - How to check if a process id (PID) ...

    • 9 Answers
  • database - Oracle: Changing VARCHAR2 column to CLOB

    • 11 Answers
  • What's the difference between HEAD, working tree and index, in ...

    • 10 Answers
  • Amazon EC2 Free tier - how many instances can I ...

    • 0 Answers

Stats

  • Questions : 43k

Subscribe

Login

Forgot Password?

Footer

Follow

© 2022 Stackoverflow Point. All Rights Reserved.

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.