It’s you again...you have to believe that Google is a good partner, helper, and confidant in your studies!
–––
This is nano editor, how to save files in Google nano editor. I'm used to vim, but this product is really hard to use! And the git commit information command should be——
The reason why this interface exists is because if you just enter git commit without entering git commit -m "commit description text", the editor will be called to edit the submission description text. Your system calls nano by default. After editing, you can press ctrl + o and press Enter to save, and then ctrl + x to exit. After exiting, the git commit will be completed and then proceed. Of course, git commit -m "commit description text" is generally recommended.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It’s you again...you have to believe that Google is a good partner, helper, and confidant in your studies!
–––
This is nano editor, how to save files in Google nano editor. I'm used to vim, but this product is really hard to use!
And the git commit information command should be——
The reason why this interface exists is because if you just enter git commit without entering git commit -m "commit description text", the editor will be called to edit the submission description text. Your system calls nano by default. After editing, you can press ctrl + o and press Enter to save, and then ctrl + x to exit. After exiting, the git commit will be completed and then proceed. Of course, git commit -m "commit description text" is generally recommended.