This commit is contained in:
Tom Willemse 2024-02-05 22:49:43 -08:00
parent a8d8799aca
commit 9c3d48cce6

View file

@ -0,0 +1,16 @@
#+title: TIL: How to Escape a Backtick in Markdown
#+tags: til
#+comments: on
#+status: publish
#+DATE: Tue, 06 Feb 2024 06:47:35 GMT
#+UPDATE_URL: /admin/modify-post/2024%252f02%252f06%252ftil-how-to-escape-a-backtick-in-markdown
I needed to send a bit of inline code in some Markdown today and it needed to have a == in it. I realized I hadn't done that before. I write code with == in it somewhat frequently because Lisp uses it for quasi-quoting, but I always write everything in org syntax where you can use either ~=~ or =~=. But in Markdown if you need to have a == in your inline code you need to wrap your inline code with more == characters.
#+begin_src markdown
`This is some inline code`
``This is some inline code with a ` (backtick) in it``
```This is some inline code with `` (two backticks) in it```
#+end_src
It looks like the sky might be the limit.