Documentation: wildcard character * interpreted by markdown
See original GitHub issueI noticed this on the azure storage blob upload
command for the --if-none-match
option. *
is a special character in markdown and should be escaped, or matched pairs will become a marker for an italicized block.
I’d have updated the markdown file, but I suspect this page was generated, and I would need the escape character added upstream to prevent it from being clobbered.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:19 (15 by maintainers)
Top Results From Across the Web
4.16 Escape special characters | R Markdown Cookbook
Some characters have special meanings in the Markdown syntax. If you want these characters verbatim, you have to escape them.
Read more >Enabling the Question Mark Wildcard Behavior in a .NET ...
character is interpreted as a wildcard and the index only returns documents containing terms that match wildcards plus one (any) character at the...
Read more >Markdown Cheatsheet - CFEngine 3.14 Documentation
First we promise to define my-illegal-class . When the promise is actuated it is automatically canonified and defined. This automatic canonification is logged ......
Read more >A Markdown Interpreter for TeX - CTAN
Unless you convert markdown documents to TEX manually using the Lua ... 2.2.3.7 Special Character Renderers The following macros replace any ...
Read more >MultiMarkdown User's Guide - GitHub Pages
Search Paths; Wildcard Extensions; Transclusion Preprocessing ... The idea is that a Markdown-formatted document should be publishable as-is ...
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
@nbering It is fixed now. Thanks for your feedback. And @daxianji007 thanks a lot for quick action. Also thanks @adewaleo for keeping track of this issue.
Confirmed fixed. Good word!