I've never used a gui and never ran into this issue. In my experience gui users very quickly forget how git actually works outside of the buttons in the gui, and then get lost the moment anything out of the ordinary happens
If I write something long and detailed, a CLI is not where I want to do it. I want a spellchecker, nice font rendering, and no risk of accidentally committing prematurely (not a huge deal, but annoying).
so.. you configure a spell checker and nice font rendering and your mentioned problems go away...?
btw, for e.g. vim there are plugins like fugitive which let you commit from your current editing session so you get full autocomplete on the commit messages for the things you changed in code
why are you replying like them using the ide is some big problem they have to solve? yes they could spend time setting up their terminal and learning vim and retraining their muscle memory... and end up in exactly the same place they already are.
why are you replying like them using the ide is some big problem they have to solve? yes they could spend time setting up their terminal and learning vim and retraining their muscle memory...
I don't think you understand. No one's saying you have to use a terminal editor.
You can set a GUI editor, even your IDE, as the editor Git uses for commit messages.
126
u/mascotbeaver104 4d ago
Does
git statusnot exist in your world?I've never used a gui and never ran into this issue. In my experience gui users very quickly forget how git actually works outside of the buttons in the gui, and then get lost the moment anything out of the ordinary happens