mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 01:05:55 +03:00
[GH-ISSUE #455] Prefer backslash over two spaces for line breaks #2226
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#2226
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thernstig on GitHub (Nov 3, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/455
Most editors and code review tools often highlight trailing white-space as a "fault". Either marking them red or similar.
Since commonmark supports both two spaces or a backslash to render a line-break, could this tool add a rule to only recommend backslash, due to the above mentioned reasons?
Resource: https://commonmark.org/help/tutorial/03-paragraphs.html
@DavidAnson commented on GitHub (Nov 3, 2021):
Yes, probably like: line-break-style and spaces/backslash/consistent
@thernstig commented on GitHub (Nov 4, 2021):
And I think backslash should be default, or consistent. Due to backslash helping with the trailing white-space issue. But I assume that would be a breaking change.
@DavidAnson commented on GitHub (Nov 4, 2021):
Right, in rules where "consistent" is an option, it is the default.