Fix PGML Emphasis in the PG CodeMirror editor.

[drgrice1]

Really, the fix has been published in an updated pg-codemirror-editor package (actually the bug was in the codemirror-lang-pg package). This just updates the version in the package.json file.

This was observed by @somiaj in #2595 (see #2595 (comment)). It turns out the problem was an error in converting from the Perl substr method to the JavaScript substring method. The code actually uses the JavaScript slice method now.

[somiaj]

This fixes the issue, thanks. I also notice that if using double ** or __ for strong/emphasis, that there is a bit of issue with the matching/formatting.

Also seems PGML doesn't require balance here, and will match any number of * or _ on both ends, so this works but the syntax highlighting should probably also match all characters not just the first.

[drgrice1]

I can fix that. Note that PGML allows it, but it isn't documented that it should work. Why would you do that anyway?

[drgrice1]

I have fixed the emphasis delimiter length (for those who unintelligibly want to type extra characters).

[somiaj]

I am just in the habit of using two delimiters from other markdown implementations and PGML has always accepted it, so that is what I noticed initially. I just decided to see what PGML would do if I didn't have matching numbers, and it seemed to not care. I guess I never noticed the using of two delimiters wasn't documented. So I would never use unmatching delimiters, but often use two.