Hi Guys,
Can’t anyone help with how to resolve the issue with setting vscode as git default editor?
I get “hint: Waiting for your editor to close the file… error: cannot run vscode: No such file or directory
error: unable to start editor ‘vscode’”
each time I run git config --global -e.
and I still got
hint: Waiting for your editor to close the file… error: cannot run vscode: No such file or directory
error: unable to start editor ‘vscode’
Editing is not diffing. You set the default editor with git config --global core.editor "code --wait" to VSCode if code is in your path. Otherwise replace “code” with the full path to the executable.
Just so everything is clear, why are we redirecting to VScode?
VScode has version control integrated and git is an independent CLI tool. So why we’d have to open VScode with git… so why we’d need to open an editor is confusing.
@Jonathan ?!? @joshuamwolfe’s link tells you exactly to do what I told you to do. Which is BTW exactly what Mosh told you to do.
You set vscode as your default editor while you should have set it to code.
I followed the instructions on the link and also what Mosh gave in this lecture but I still get “zsh: command not found: code” when I run code audience.txt
hello jonathan did you find the solution to the problem to this error when executing the command git config --global -e, I get the same error as you, I await your response thanks.
hint: Waiting for your editor to close the file… code --wait: code: command not found
error: There was a problem with the editor ‘code --wait’.