Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
In project changelog Markdown files, list items are hard-wrapped in the source at a fixed column length (normal editor wrapping for readability).
In Cursor’s in-editor Markdown Preview, those source newlines are shown/applied as visual line breaks, so each list item breaks multiple times and the preview looks wrong.
Other Markdown previews I’ve used (including typical CommonMark/GitHub-style rendering) treat a single newline inside a paragraph/list item as a soft break / space, and only start a new visual block on a blank line (or an explicit hard break like two trailing spaces / backslash). Cursor Preview appears to honor source line breaks more literally, which makes wrapped changelogs hard to read.
Steps to Reproduce
-
Create or open a Markdown changelog with a list item hard-wrapped across multiple source lines, for example:
- This is a long changelog bullet that is wrapped in the
source file at a fixed column so the Markdown stays
readable in the editor.
- This is a long changelog bullet that is wrapped in the
-
Switch to in-editor Preview (Markdown/Preview toggle).
-
Observe that the list item visually breaks at each source newline instead of flowing as one continuous bullet.
-
Compare with classic Markdown preview (Ctrl+Shift+V) and/or GitHub rendering, where the bullet typically reads as one wrapped paragraph.
Expected Behavior
Hard-wrapped source lines inside a list item should render as continuous flowing text (soft wrap), not as multiple forced visual breaks—consistent with common Markdown previewers and VS Code/GitHub-style rendering.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
3.13.25 (user setup)
Additional Information
- Common in changelog files where lines are wrapped for source readability.
- I searched the forum and did not find an existing report for this specific rendering behavior.
- If the Preview intentionally uses a “literal newlines” / soft-break style, a setting to match CommonMark/GitHub would help.
Does this stop you from using Cursor
No - Cursor works, but with this issue
