-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insert hard newlines instead of wrapping long lines #52
Comments
Nice to see you here / on Commit :)
Not sure if you're talking about the current setting but there is no hard limit - just a "hint" for the subject line. The goal is not to wrap but to help the user knowing when it exceeds the max length on Github/Gitlab/... What you are talking about would be a new setting for https://robertcooper.me/post/git-commit-messages#body-line-length-limited-to-80-characters correct ? If so - here is what I can do
|
Yes. Basically, right now the commit message is just wrapped in the UI by the text input; the underlying content is a single line. While some people do use this style, it's kind of broken on the CLI. Additionally, it messes up any formatting.
It would probably help; I mostly gleaned it was about the commit subject because it was set to 50 characters, but it's not overly clear.
This would, indeed, be the thing I'm asking. |
Could you elaborate a little or link to documentation / example? |
I came here to report the same issue, I got tricked by the small window until I noticed the very long line commit on gitlab |
@bilelmoussaoui any chance you can share that commit url - I want to make sure we are talking about the same thing |
Commit should not put the entire commit message on as few lines as possible: it makes reading commit messages harder than necessary on the command line.
If the user specifies a hard limit for the length of each line, the commit message should be following that size. This should be possible by iterating over the text using Pango, and finding where words wrap.
The text was updated successfully, but these errors were encountered: