spurious warnings about question or exclamation marks in a header
See original GitHub issuea header like this one:
# Why?
produces a MD026
warning about trailing punctutation in the header. the same happens when an exclamation mark is used.
this should not happen.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Irony punctuation - Wikipedia
Irony punctuation is primarily used to indicate that a sentence should be understood at a second level. A bracketed exclamation point or question...
Read more >Periods, exclamation marks, and question marks - Graduate ...
Question marks appear inside quotation marks, parentheses, or brackets only when part of the quoted or parenthetical material: · Question marks appear outside ......
Read more >Five! Is too many! | Get It Write
“An excessive use of exclamation marks is a certain indication of an unpractised writer or of one who wants to add a spurious...
Read more >The Full Stop, the Question Mark and the Exclamation Mark
The exclamation mark (!), known informally as a bang or a shriek, is used at the end of a sentence or a short...
Read more >How to Spot Fake News - FactCheck.org
Among them: an anonymous author; excessive exclamation points, ... news” or satire warning, like WTOE 5, which published the bogus headline, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fair enough. 😃 For what it’s worth, this rule came from the Ruby implementation. I’ll admit it’s not my absolute favorite rule, but I think it’s a good guideline in general, it’s easy to turn off if you don’t want it, and it’s easy to customize when needed. I’m not inclined to break compatibility with the Ruby implementation over something like this, so unless you find that the rule is behaving wrongly, I will recommend turning it off. Sorry for the inconvenience!
What do you think is wrong here?
The documentation for
MD026
explicitly calls out that it will trigger for?
and!
: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md026---trailing-punctuation-in-headerIf you do not like this rule, it can be disabled completely - or you can edit the list of characters it looks for (again, see documentation above).