github-flavored-markdown-escape-backticks.md

GitHub-flavored Markdown does not use C-style escapes for escaping backticks inside spans. Instead, GFM uses double, significant whitespaced, backticks.

Two backticks, then a space, then a backtick, then a space, then two more backticks:

`` ` ``

produces:

`

That's interesting... thanks for the analysis.

How would one avoid the superfluous space when, say, using MySQL-style reference notation in a quoted block? For example:

In MySQL, we use `table`.`column`...

See what I mean? The extra spaces appear in the output.

Furthermore, the table and column do not receive the pre-format styling.

The stuff between the double backticks is escaped so your example would look exactly the same surrounded by a pair of double back ticks.

`` `table`.`column` ``

To my future @dwiyatci self: if you only wanna escape backtick in regular text (not code), simply use \ (backslash) to escape it. Source here.

`Good night, Glenn.`

`
``
```
````
...

Can you quote backticks inside a code block inside a GitHub issue title? Using double backticks as the delimiter doesn't work in that context.

@patbl

To display triple backticks in a fenced code block, wrap them inside quadruple backticks ````.

```
Look! You can see my backticks.
```

https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks

@jonathanneo I was asking about GitHub issue titles. It seems like you can't use fenced code blocks in titles because they have just one line. Or am I missing something?

@patbl I missed the part about issue titles. I'm not sure in that case.

@patbl @jonathanneo github/docs#24940