You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 28, 2022. It is now read-only.
I'm wondering if line wrapping is necessary for markdown files (or any files for that matter). Apparently, Github can show the code with soft wraps and I suppose IDEs can do this too? In that case, inserting hard line breaks seem like a waste of effort.
The text was updated successfully, but these errors were encountered:
Yes, in fact I feel that inserting hard line break should be discouraged for markdown documentation. Adding new words or removing words will make the wrapping out of sync, and correcting it will just add noise to the diff.
Yes, in fact I feel that inserting hard line break should be discouraged for markdown documentation. Adding new words or removing words will make the wrapping out of sync, and correcting it will just add noise to the diff.
I feel the same way.
I wish we could do the same in more places, such as commit message body and javadoc comments (basically, places where we use prose).
I'm wondering if line wrapping is necessary for markdown files (or any files for that matter). Apparently, Github can show the code with soft wraps and I suppose IDEs can do this too? In that case, inserting hard line breaks seem like a waste of effort.
The text was updated successfully, but these errors were encountered: