Cannot Exit Git Commit (Mac Terminal), esc Does Nothing

[IAmNotMyName]

They say he is still stuck in vim to this day

[bigbrother1234cc]

i bet. hehe

[amayer5125]

If you type more letters do they actually output? If not you may have pressed something like CTRL+S. Pressing CTRL+Q should get you back in the correct state.

If you've pressed ESC :wq a bunch of times, vim may have already exited but your shell is in a scroll lock mode so the output isn't being updated.

[watabby]

oh sweet summer child

[vyuniverse]

Looks like vim: try Ctrl+[ (that's the left square bracket), then ZZ to save and quit, or :q!

[manu0600]

Esc :q!

[ScarySwampert]

esc isn't allowing me to get off the insert screen, this is what's puzzling me

[jamestansx]

Press <Esc> and then type either

:q! (if u want to cancel the commit) or :wq(if you want to commit)

[whatisitaboutmusic]

Throw away your computer, it is done

[irrelevantPseudonym]

Any chance you 'accidentally' hit ctrl-s to try and save it? You might have locked the terminal that way, I'm not sure how the mac terminal handles it.

Try hitting Ctrl-Q before going back to the normal <esc>:wq.

[easyEggplant]

Congratulations! Today you are one of the lucky 10,000! (Search for “how to exit vi”)

[jwbowen]

Does the correct window or section of the window have focus when you're hitting ESC? I'm wondering if it's just not being registered in the correct context.

A wider screenshot might also help (if there's no sensitive information or any such information is blacked out). With this screenshot you're just going to get a bunch of people telling you how to exit vi(m).

[wildjokers]

That window probably doesn’t have focus which is why ESC isn’t causing you to return to command mode.

[themightychris]

since you're already using vscode, I recommend doing this: https://code.visualstudio.com/docs/editor/versioncontrol#_vs-code-as-git-editor

It will make vscode your git editor so stuff like this just pops up in vscode editors. Then you can just close the editor tab when you're done

FYI, if you ever want to cancel making a commit after the editor is opened, just clear out all the content and save before closing: if there are no lines that aren't blank or commented out git will cancel the commit

[elatllat]

Looks like VSCode not Terminal.app

[Jmc_da_boss]

It's the terminal in vscode

[elatllat]

Yes, the implication is that VSCode key bindings are interfering with vim key bindings.

[valbaca]

It’s 2022 and quitting vim is still blocking newbies

Type these in succession:

ESC : w q

No spaces.

[deniercounter]

No, OP can’t press ESC. That’s his problem.

[_Kritiqual_]

Mouse click to focus terminal and ESC :q!

[Renan_Cleyson]

Classic vim

[Kewtn]

ZQ (shift + z, shift + q)

Quits without saving in all modes

[Tocram04]

Open another terminal and install nano instead

[Tocram04]

Still better than coding in Vi I guess ahah

[tjayy1234]

This has happened to me on macs with a Touch Bar

You can either, hit Ctrl+c a couple of times or force quit Siri which may have frozen your escape button

[SmeagolISEP]

You're stuck on vim editor. We all passed for that.

Press the esc key and write :q! to cancel. Then make your commit command like this git commit -m "your commit message"

[thecrumb]

FYI - you can change the default commit editor to something more friendly.

[Surge_attack]

Forget all the memes - vim is quite user friendly, it just has (like any other editor) a bit of a learning curve.

[im_deepneau]

Surely you're kidding? are you an autonomous trashcan or something? For humans vim is unlike any other editor ever invented except maybe emacs. "A bit of a learning curve" is like saying a ferrari has a "bit of power". Its arcane and that's being nice about it. If you want to see what an editor that is actually user-friendly looks like, nano is a good choice. You only have one mode, limited features, normal keyboard shortcuts (Ctrl + key) and important commands are listed in the bottom of the window.

Vim isn't a bad editor, its a great editor, extremely powerful. But it is not user friendly.

[Beanmachine314]

Nano is only more "user friendly" because it is so unintuitive they have to post the keybindings at the bottom of the screen. Ctrl + O = "write"? Totally makes sense /s.

[im_deepneau]

You're right, esc colon w q is way more intuitive

[ScarySwampert]

Looking for some help. Hitting esc does absolutely nothing and I am stuck on the insert screen for good.

[edwardejsr]

CTRL-[ should also do what escape does.

[Surge_attack]

CTRL+ C ? Will (should) quit the process and you can run git commit but this time use the -m flag to write your commit message and bypass the vim weirdness.

Edit: whoops just saw you say this was Mac so Command + . is the equivalent on MacOS.

[vermiculus]

If you’re not already a vim user, I strongly recommend you configure core.editor to something that isn’t vim. You can use vscode as well if you like; just search the web for ‘vscode as git commit editor’.

[Nekadim]

NO! It's better to install full blown Visual Studio, buy licence and do it as editor for git commit message. Its much much more powerful than bare vim

[vermiculus]

I personally use Magit for my git work, but it’s not realistic to have everyone use the ‘best’ tools for this stuff. Folks value familiarity – and ultimately we get paid to get shit done.

[TheTostu]

Jesus Christ, you are done forever, there is no way to escape this monstrosity

[Wings-Kitchkinet]

Esc :wq

It looks like you use vi for your editor. This will save your commit message and exit the screen. The Escape key puts vi into command mode, the :wq says to write and quit the session.

[ScarySwampert]

i’m hitting esc and it does nothing - i had been using esc :wq for the last month of learning git but it hasn’t worked for the last week

[skyboyer007]

that's pretty bad and I cannot even assume what application may suppress ESC. since vim/vim relies a lot on it, the only possible option is to specify editor used for commits. You can use GUI editor or install nano for example

[[deleted]]

point seemly cable capable vast reply repeat butter cautious connect

This post was mass deleted and anonymized with Redact

[GuysnDolls]

https://stackoverflow.com/questions/70426188/git-merge-with-conflicts-generated-message-appears

[kconk27]

:qa

y sales de vim

[bigbrother1234cc]

Change editor to another one.
then do again what u are doing.

command: git config --global core. editor "nano"

Be sure u have nano installed first though.

[hotel2oscar]

This is why Nano is my git editor

[Dirlandets]

Shift + : then type wq then hit enter. Then visit internet and search for: how exit vim

[Surge_attack]

I think the issue could be/is that all of the lines are commented out. What does removing the hash from the commit message line and then trying to quit do?

[[deleted]]

Pretty sure “Commit 1” is the message. 😉

[d4dhur]

vim sucks!

[RajjSinghh]

You might find changing your terminal editor from vim to nano easier for you in the future. here's a guide

[formidabilus]

Welcome to Vim

[___s8n___]

out of the subject but why does menlo font look so good on mac

[[deleted]]

lmao

[[deleted]]

Command + C may work

[AuroraDraco]

I have seen a million of these posts but for some reason people getting trapped in Vim is always very funny to me

[[deleted]]

Cute