[GH-ISSUE #301] Idea of new rule: use slash instead of backslash for image path #257

New issue

Open

opened 2026-03-03 01:25:11 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:25:11 +03:00

Owner

Originally created by @skyoxZ on GitHub (Jun 30, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/301

Correct:

![foo](images/foo.jpg)

Not recommended:

![foo](images\foo.jpg)

Originally created by @skyoxZ on GitHub (Jun 30, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/301 Correct: ``` ![foo](images/foo.jpg) ``` Not recommended: ``` ![foo](images\foo.jpg) ```

kerem added the

new rule

label

2026-03-03 01:25:11 +03:00

kerem commented

2026-03-03 01:25:12 +03:00

Author

Owner

@thawk commented on GitHub (Jul 7, 2022):

What's the state of this rule? It seems that markdown document written in typora use backslash for image path, it make the image broken in gitlab.

@thawk commented on GitHub (Jul 7, 2022): What's the state of this rule? It seems that markdown document written in typora use backslash for image path, it make the image broken in gitlab.

kerem commented

2026-03-03 01:25:12 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 7, 2022):

It sounds like a fairly straightforward rule to implement if anybody wants to do so for npm or as a custom rule in their repository. I have not added it to the core library so far.

@DavidAnson commented on GitHub (Jul 7, 2022): It sounds like a fairly straightforward rule to implement if anybody wants to do so for npm or as a custom rule in their repository. I have not added it to the core library so far.

kerem referenced this issue

2026-03-07 20:04:15 +03:00

[GH-ISSUE #257] MD018 incorrectly flags the #️⃣ emoji #2068