Live data from Hacker News

Why you should use a terminal editor to write a commit message

joaomagfreitas.link

31–32 of 32 posts

Re: Why you should use a terminal editor to write a commit message

#31
The main reason to use an editor is not included: multi-line commit meesages

I continue to see commit messages by people using IDEs that have long single line commit messages.

A short summary line, which shows as the one line commit message in gitk et al, then a detailed commit messages that can be pages long in some cases is the ideal form.

Some commits only need a 1 line message, but others need long detailed blocks of text. When this is the case, having that short summary, and a blank line separating the lengthy details gives correct presentation in all git tools.

Re: Why you should use a terminal editor to write a commit message

#32
Mh...

1. err, firing up an editor, type the message, save and quit is not quicker...

2. on my keyboard they are on a single key (I have inverted number/symbol row), my environment (Emacs/EXWM for some things my QMK firmware) automatically pair relevant symbols)...

5. various shells have history, easy navigation etc, so well... Not that hard...

6. I hardly imaging putting special chars in a commit message...

To me the main reasons might be: commit messages should often have a short line title THAN a more broad prose, witch is a good reason to use an editor. If your editor is not nano but something more featuresful you might like templates and so on. The rest seems to be a bit... Considerations by someone who not use much a shell, so it's not comfortable with it.

Post reply on HN