4 ms·
I personally don't like hard wrapping the body of a commit message because it then looks terrible every where - GitHub website, git client etc. and it becomes m
by indentit 7y ago
I personally don't like hard wrapping the body of a commit message because it then looks terrible every where - GitHub website, git client etc. and it becomes much harder to read
- jklm 7y agoThat’s interesting, IIRC short lines are supposed to increase readability because longer ones are harder to mentally wrap.
- ceejayoz 7y agoSure, but there’s no reason that has to be done manually. Leave it to the client.
- yawaramin 7y agoMost clients don't wrap in a way that helps readability, though. Look at Hacker News comments for example. At 1:1 zoom the text is spread out across the screen in super-wide lines that are hard to read. The classic recommended 72-char hard wrap guarantees a good reading experience on all but the narrowest of screens.
- Reelin 7y agoI often browser HN in a half width window for this exact reason. To be clear, I don't fault HN for this; I can trivially resize my window to whatever works best for me. Commit messages are different because people often interact with them via command line based tooling.
- u801e 7y agoWhat about parts of the commit messsage that shouldn't be wrapped and having them wrapped hurts readability? If you rely on soft-wrapped, then there's no way to prevent that from happening.