I'm trying to use CodeMirror simple mode to create my own editor and highlight some custom keywords. However, it's highlighting occurrences of these words inside other words. Here's my code to define the mode of the editor:

    CodeMirror.defineSimpleMode("simple", {
  // The start state contains the rules that are intially used
  start: [
    // The regex matches the token, the token property contains the type
    {regex: /["'](?:[^\\]|\\.)*?(?:["']|$)/, token: "string"},
    {regex: /;.*/, token: "ment"},
    {regex: /\/\*/, token: "ment", next: "ment"},

    {regex: /[-+\/*=<>!]+/, token: "operator"},
    {regex: /[\{\[\(]/, indent: true},
    {regex: /[\}\]\)]/, dedent: true},

    //Trying to define keywords here
    {regex: /\b(?:timer|counter|version)\b/gi, token: "keyword"} // gi for case insensitive
  ],
  // The multi-line ment state.
  ment: [
    {regex: /.*?\*\//, token: "ment", next: "start"},
    {regex: /.*/, token: "ment"}
  ],
  meta: {
    dontIndentStates: ["ment"],
    lineComment: ";"
  }
});

When I type in the editor, this is what gets highlighted. I would expect the first two occurrences to be styled, but not the second two.

It's obviously something incorrect with this regular expression:

/\b(?:timer|counter|version)\b/gi

But I've tried it several different ways and the same pattern works correctly in other regex testers. Example: . Any advice?

Edit #1:

Tried this pattern in codemirror definition, dropping the /g but it still yields the same incorrect highlighting.

{regex: /\b(?:timer|counter|version)\b/i, token: "keyword"}

I'm trying to use CodeMirror simple mode to create my own editor and highlight some custom keywords. However, it's highlighting occurrences of these words inside other words. Here's my code to define the mode of the editor:

    CodeMirror.defineSimpleMode("simple", {
  // The start state contains the rules that are intially used
  start: [
    // The regex matches the token, the token property contains the type
    {regex: /["'](?:[^\\]|\\.)*?(?:["']|$)/, token: "string"},
    {regex: /;.*/, token: "ment"},
    {regex: /\/\*/, token: "ment", next: "ment"},

    {regex: /[-+\/*=<>!]+/, token: "operator"},
    {regex: /[\{\[\(]/, indent: true},
    {regex: /[\}\]\)]/, dedent: true},

    //Trying to define keywords here
    {regex: /\b(?:timer|counter|version)\b/gi, token: "keyword"} // gi for case insensitive
  ],
  // The multi-line ment state.
  ment: [
    {regex: /.*?\*\//, token: "ment", next: "start"},
    {regex: /.*/, token: "ment"}
  ],
  meta: {
    dontIndentStates: ["ment"],
    lineComment: ";"
  }
});

When I type in the editor, this is what gets highlighted. I would expect the first two occurrences to be styled, but not the second two.

It's obviously something incorrect with this regular expression:

/\b(?:timer|counter|version)\b/gi

But I've tried it several different ways and the same pattern works correctly in other regex testers. Example: https://regex101./r/lQ0lL8/33 . Any advice?

Edit #1:

Tried this pattern in codemirror definition, dropping the /g but it still yields the same incorrect highlighting.

{regex: /\b(?:timer|counter|version)\b/i, token: "keyword"}

• javascript
• regex
• codemirror

Share Improve this question Follow edited Jun 20, 2020 at 9:12 CommunityBot 111 silver badge asked Nov 22, 2016 at 15:29 colinwurtzcolinwurtz 72311 gold badge77 silver badges2626 bronze badges 5

• 1 You should drop the /g modifier: /\b(?:timer|counter|version)\b/i. I don't know if it's the cause of your problem, but it definitely isn't needed. Otherwise, the regex looks fine. – Alan Moore Commented Nov 22, 2016 at 16:26
• @AlanMoore Thanks, I did try that but still got the same result. Removing the /gmodifier limited my matches here though. – colinwurtz Commented Nov 22, 2016 at 16:55
• What does it do with the word timerNO? That is, does the \b at the end work? – Alan Moore Commented Nov 22, 2016 at 17:06
• 1 @AlanMoore this pattern {regex: /\b(?:timer|counter|version)\b/i, token: "keyword"} does not highlight timerNO. Does it seem like it's not respecting the /b at the beginning? – colinwurtz Commented Nov 22, 2016 at 17:13
• 1 I suspect it's treating the beginning of the match as the beginning of the string. If that's the case, then a regex like /\b!bar/ won't match anywhere, even in foo!bar. – Alan Moore Commented Nov 22, 2016 at 17:30

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 6

I ended up just defining my own mode from scratch and the additional customization seems to have worked. I parse the stream by word, convert to lowercase, then check if it's in my list of keywords. Using this approach it seems very straightforward to add additional styles and keywords.

var keywords = ["timer", "counter", "version"];

CodeMirror.defineMode("mymode", function() {

  return {
    token: function(stream, state) {
      stream.eatWhile(/\w/);

      if (arrayContains(stream.current(), keywords)) {
        return "style1";
      }
      stream.next();
    }
  };

});


var editor = CodeMirror.fromTextArea(document.getElementById('cm'), {
  mode: "mymode",
  lineNumbers: true
});

function arrayContains(needle, arrhaystack) {
  var lower = needle.toLowerCase();
  return (arrhaystack.indexOf(lower) > -1);
}

Working Fiddle