Don't grey-out literals (characters following a backslash) about zettlr HOT 4 CLOSED

I see where you get to but this is rather monkey patching-like. I'm not sure that's the best way. In the past months when I was developing Zettlr, I always resorted to monkey-patching. This way I could cramp into the app many features as quickly as possible, and now I'm stuck with a lot of code refactoring. Besides, a simple document.replace wouldn't suffice, as CodeMirror internally does a lot of stuff to the text before it is actually rendered. I guess we're stuck with two options:

1. Manually adapt the gfm-mode to divide between the escaping character and the literal (which I would prefer)
2. Add an option to either grey out both, or none of the characters.

As the gfm-mode itself is just a superset of the markdown-mode, maybe there's a way to override this behaviour manually. If so, I'll stick with this, but this requires some more research.

from zettlr.

Yep, this is a problem in the underlying Markdown parser from Codemirror, which does not differentiate between the escaping backlash and the literal character. It has annoyed me for some time myself. The problem would be that, if I manually alter the Markdown parser code then I won't be able to integrate CodeMirror updates so easily in the future, which is why I'm rather hesitant in doing this. I'll look into the chances of doing so!

from zettlr.

I see that the class cm-formatting-escape is applied to the whole text \[, so pure CSS wouldn't work.

But a combination of a regex like:

document = document.replace(/\\([[\]@])/ig, '\\<span class="nogrey">$1</span>');

together with a custom CSS rule for the nogrey class could work? Tested on Regex101: https://regex101.com/r/Jq7xVr/3

EDIT: Added @ to the regex (so it recognizes \@ as well as \[ and \]) and removed redundant backslash

from zettlr.

Tada!

from zettlr.