Colon (`:`) between 2 words in header disappears

[sylwekb]

Hey,

I use a header like this:

### `/autocontrast:3/`

The result is:

And the html looks like this:

Tried on Firefox and Chrome, in both cases the :3 is missing. I have the noEmoji: true, setting but it seems docsify still tries to parse.

Please help :)

[cheng-kang]

FYI: https://daringfireball.net/projects/markdown/syntax#backslash

`/autocontrast:3/`

/autocontrast:3/

// Correct
### \`/autocontrast:3/\`

// Wrong
### `/autocontrast:3/`

[sylwekb]

Hey, thanks for a quick answer, unfortunately it didn't work:

### \`/autocontrast:3/\`

Produces:

[cheng-kang]

Ah, sorry, I missed the :3 part. My guess is that the problem is with config parsing. Because Docsify allows users to configure by adding :CONFIG_NAME=CONFIG_CONTENT.

Will check later.

[sylwekb]

... Docsify allows users to configure by adding :CONFIG_NAME=CONFIG_CONTENT.

Thanks! I would be equally happy with a workaround if a proper fix is too complicated ;) Can you point to the documentation which describes this :config behavior? For me it looks like it's alias https://docsify.js.org/#/configuration?id=alias but i'm not sure nope, sorry, just noticed it's for routes

[cheng-kang]

This page describes a few configs you can use: https://docsify.js.org/#/helpers?id=customise-id-for-headings

[sylwekb]

To everybody who has the same problem. The regexp is here. The workaround I found is to use other colon: https://unicode-table.com/en/A789/
Normal colon: :
Modifier Letter Colon: ꞉

[sylwekb]

Just realized it's not good workaround if you allow users to copy it and use somewhere where the fact that it's a real colon is important ;D

[sylwekb]

AFAIU It does not make sense to set more than 1 id for heading, so it's enough to remove g at the end of the regexp https://github.com/docsifyjs/docsify/blob/v4.8.5/src/core/render/compiler.js#L22

[QingWei-Li]

We should allow the user to use the content of :xx=yy, just match it to when \:xx=yy will not be processed.

[vsespb]

We should allow the user to use the content of :xx=yy, just match it to when \:xx=yy will not be processed.

We're affected by current bug and we use same Markdown in docsify and NOT in docsify at same time. So adding escapes like this \:xx=yy to all our markdown will damage it for world outside of docsify.

maybe use this PR instead #708
i.e. process configs only when there is a space/start of line before colon.

[Kikobeats]

Related: #698