Re-add soft line breaks to GitHub-flavored-markdown #10981
Replies: 6 comments 8 replies
-
Agreed. Please restore the behavior described in the docs! (Or, failing that, fix the docs.) |
Beta Was this translation helpful? Give feedback.
-
I just ran into this problem. All my Is there a good reason to change this long-existed feature? |
Beta Was this translation helpful? Give feedback.
-
Wow. Typically I read my own markdown in my text editor, where having long lines of text is terrible. Just noticed the behavior in my repository, where I now have hard line breaks and... it looks terrible. This was a very surprising and distressing change. Please restore the old functionality. Example of text that displayed at full width until recently: https://github.com/Ed-Fi-Exchange-OSS/Suite-3-Performance-Testing/blob/main/README.md |
Beta Was this translation helpful? Give feedback.
-
Different repos have different needs. I want hard line breaks because I write poetry, and don't want to add |
Beta Was this translation helpful? Give feedback.
-
Was the change also reverted for GitHub releases? It seems like the release notes still render every line-break, even within a markdown paragraph. |
Beta Was this translation helpful? Give feedback.
-
Would be nice if enter was a hard line break, and shift+enter was what it currently was. Would be faster than two spaces. |
Beta Was this translation helpful? Give feedback.
-
Markdown supports soft line breaks, but it seems that GitHub flavored markdown has removed support for it. This is a real shame because it means I have to spend extra time re-formatting any github-destined markdown auto-generated markdown that is auto-generated from my commits (which have a hard line limit of 72 chars) because the resulting rendered text will have the same line breaks.
Here is an example block of text. This is formatted using a hard
72-character line limit, like I use for all my commits (and thus
auto-generated text like single-commit PR messages and semantic-release
changelogs).
Here is another block of text, but this time it's written as a single really long line. This is easy to type into the github text boxes, but that's not the only place text comes from. Why was support for soft-wrapping removed in the first place?
As you can see, the first block is not using soft-wrapping, despite each line ending in a single newline character (no spaces, no double newlines). I don't know if this is a bug or if it was an intentional change, but either way I would really appreciate it if it were changed back to allow standard markdown soft wrapping.
Beta Was this translation helpful? Give feedback.
All reactions