Skip to content

Commit efff8bc

Browse files
committed
Change HEX value highlighting to be optional
HEX value highlighting should be optional because Markdown does nothing on it. It is only an eye candy. It can be triggered in the json key "extraHighlight", and its default value is `false`. More similar highlighting that is not Markdown-related syntax will become available using this key.
1 parent 43b6ec5 commit efff8bc

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

build/data.template.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
"default": {
44
"fgColor": "",
55
"bgColor": "",
6+
"extraHighlight": false,
67
"transparentBg": false
78
},
89
"header": {

build/userDefinedLang-markdown.template.classic.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@
77
<KeywordLists>
88
<Keywords name="Comments">00# 01 02((EOL)) 03&lt;!-- 04--&gt;</Keywords>
99
<Keywords name="Numbers, prefix1"></Keywords>
10-
<Keywords name="Numbers, prefix2">0x</Keywords>
11-
<Keywords name="Numbers, extras1">A B C D E F</Keywords>
10+
<Keywords name="Numbers, prefix2">{{#default.extraHighlight}}0x{{/default.extraHighlight}}</Keywords>
11+
<Keywords name="Numbers, extras1">{{#default.extraHighlight}}A B C D E F{{/default.extraHighlight}}</Keywords>
1212
<Keywords name="Numbers, extras2"></Keywords>
1313
<Keywords name="Numbers, suffix1">.</Keywords>
1414
<Keywords name="Numbers, suffix2">.</Keywords>

0 commit comments

Comments
 (0)