Bug: Parsing commented out markdown syntax

[piecioshka]

When I attached:

<script src="//cdn.jsdelivr.net/npm/docsify-latex@0"></script>

to my Docsify project about something, my comment which is on the top of the main file:

<!--

```bash
npx docsify-pdf-converter

docsify serve .
\```

 -->

is rendered, which is unwanted, ofc.

[scruel]

Please create a reproducible sandbox, thanks!

[piecioshka]

Sure! @scruel pls check it - https://codesandbox.io/p/sandbox/307qqv236

[scruel]

Hi, I can't reproduce your issue:

And I think you should report this issue to the main docsify repo, not here -- since mine repo is just a plugin repo of docsify, thanks!
So I will close this issue, feel free to add comments if you don't think so.

[piecioshka]

hmm, sorry to hear that you cannot reproduce this error.
I created a repo with this issue: https://github.com/piecioshka/docsify-latex-issues-5
Please follow GitHub Pages on this repo: https://piecioshka.github.io/docsify-latex-issues-5/

Can you confirm, that you see this error?

[piecioshka]

This comment will be rendered good when I will remove this line from index.html:

<script src="//cdn.jsdelivr.net/npm/docsify-latex@0"></script>

[scruel]

I see, I know what causes this, actually, it related to the following issue:
docsifyjs/docsify#1898

The main problem here is that I currently use regex to parse the HTML to detect math block, rather than dom/ast level parsing (which will be a quite heavy job for a plugin). Based on regex, either first parse HTML comment or first parse code block all will lead to the same issue you opened, which may not a thing that this repo as a plugin repo can solve.
But I will see what I can do to "solve" this issue in a hack way.

[pauldmccarthy]

I've come across an issue which may be related to this - I often embed shell commands in my markdown files, using backslash characters to split long commands across multiple lines, e.g.:

```bash
some_command arg1 \
 -b arg2 \
 -c arg3 \
 -d final_arg
some_other_command
```

It looks like the regex used to match code blocks does not match blocks containing backslashes.

What is happening for me is that the rendering logic will detect the closing backticks as the start of a code block, and then detects the opening backticks of the next code block as closing. This has the effect that, if subsequent code blocks contain dollar-signs (e.g. using environment variables), docsify-latex will attempt to render them as latex.

I.e. for this source content:

Here is a code block which escapes newlines using backslash characters:

```bash
some_command arg1 \
 -b arg2 \
 -c arg3 \
 -d final_arg
some_other_command
```

Here is another code block which uses dollar signs:


```bash
some_command -u ${USERNAME} -p ${PASSWORD}
```

I get the following rendered content:

with the full text of the second code block:

some_command -u <!-- latex:replace  JTNDZG9jc2lmeS1sYXRleCUyMGRpc3BsYXklM0QlMjJmYWxzZSUyMiUyMHN0eWxlJTNEJTIybWF4LXdpZHRoJTNBJTIwMTAwJTI1JTNCZGlzcGxheSUzQSUyMGlubGluZS1mbGV4JTNCb3ZlcmZsb3clM0ElMjBhdXRvJTIwaGlkZGVuJTNCJTIyJTNFJTI0JTdCVVNFUk5BTUUlN0QlMjAtcCUyMCUyNCUzQyUyRmRvY3NpZnktbGF0ZXglM0U= -->{PASSWORD}

I've solved this in my own documentation by hacking the regex to search for (?:[\s\S])+? instead of (?:[^\\]|\\.)+?, which appears to solve the issue for me. I'm not sure why the original regex contains [^\\] at all - is it because it is used to match math blocks as well (e.g. searching for \\()?