Clueless designer admission:
When git kicks me into Vim I have *absolutely no fucking clue why it has happened nor how to get out of it* 😩
8
Replies
0
Boosts
…Waits for replies beginning with “just…” or “simply…” or “it’s easy…”
@urlyman first off, in your appropriate rc or profile file, set EDITOR=/path/to/the/editor/you/want/to/use...
(Game changer for me, even though I'm pretty facile in vi, it's so nice to have the familiar.)
@danlyke thanks Dan, that sounds helpful.
So what kind of 'editor' are we talking about here? What kind of options are there and why would I choose one over another?
I presume we are not talking about a text 'editor' of the kind I use to write front-end code?
@urlyman exactly the sort of text editor you'd use to write front-end code. I have mine set to emacs, but you can pop up a GUI editor as long as it takes as a parameter the file name to edit.
git creates a template file for you to annotate your checkin, and fires up the editor with it. You make your changes, quit the editor (eg: <esc>:wq<enter> in vi), and git continues the commit.
@danlyke thanks, this is sort of making sense.
I’ve just learned that I shouldn’t have said Vim, as my zsh uses vi, and Vim and vi are not the same thing.
I’m currently searching around trying to make sense of what the role of the 'editor' even is and why I sometimes need to be kicked into it.
I'm used to writing my commit messages directly in VS Code’s terminal.
The problem I always come back to is the assumed knowledge from which ‘help’ articles address things. And then I run away scared
