[GH-ISSUE #201] MD033 flagged for element with forward slash inside name #2020

New issue

Closed

opened 2026-03-07 20:03:46 +03:00 by kerem · 1 comment

kerem commented

2026-03-07 20:03:46 +03:00

Owner

Originally created by @nschonni on GitHub (Jul 3, 2019).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/201

For the <ProjectTemplates/ItemTemplates> in the following block, it get's flagged by Markdownlint, but it isn't an element that Markdown renders as html

**\<Visual Studio installation directory>\Common7\IDE\\<ProjectTemplates/ItemTemplates>**

Originally created by @nschonni on GitHub (Jul 3, 2019). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/201 For the <ProjectTemplates/ItemTemplates> in the following block, it get's flagged by Markdownlint, but it isn't an element that Markdown renders as html ```md **\<Visual Studio installation directory>\Common7\IDE\\<ProjectTemplates/ItemTemplates>** ```

kerem

2026-03-07 20:03:46 +03:00

closed this issue
added the
bug

fixed in next
labels

kerem commented

2026-03-07 20:03:47 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 3, 2019):

There are two parts of this line that look like HTML elements. The first is correctly ignored because the leading angle bracket is escaped by a backslash. The second causes a violation to be reported because the leading angle bracket is not escaped; the double backslashes there escape themselves. However, the Markdown parser does not treat the second instance as an HTML element due to the forward slash embedded in it. The regular expression used by markdownlint doesn’t know about that exceptional case.

@DavidAnson commented on GitHub (Jul 3, 2019): There are two parts of this line that look like HTML elements. The first is correctly ignored because the leading angle bracket is escaped by a backslash. The second causes a violation to be reported because the leading angle bracket is not escaped; the double backslashes there escape themselves. However, the Markdown parser does not treat the second instance as an HTML element due to the forward slash embedded in it. The regular expression used by markdownlint doesn’t know about that exceptional case.