blocks|key|2507944|text|因此，我在Sublime中测试了一系列具有多行注释的语言(C/C%2B%2B、Java、HTML、JavaScript)，但没有一种语言语法支持在多行注释中嵌入多行注释-+comment作用域的语法突出显示以第一个“注释关闭”标记结束，而不是对称标记。现在，这并不是说这是不可能的，因为BracketHighlighter插件可以很好地匹配对称标记、括号和其他标记。然而，它是用Python语言编写的，并在匹配算法中使用了自定义逻辑，这在为Sublime的语法高亮工具提供动力的Oniguruma引擎中可能是不可用的，显然也是Github's引擎所不具备的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2507945|基本上，根据您对问题的描述，您需要一个代码解析器来确保嵌套注释是合法的，这是您不能仅使用语法突出显示定义所做的事情。如果你只是为Sublime写这篇文章，一个定制的插件就可以解决这个问题，但是我对Github的语言语法突出显示系统了解不够，不知道你是否被允许这样做。我还不是regex高手，但在我看来，纯粹通过regex很难做到这一点，因为在查找(和识别)之前，您需要以某种方式跟踪任意数量的内部对称"open“和"close”标记。最后一个。|2507946|很抱歉，除了我不确定这是否可能之外，我不能提供一个明确的答案，但在不了解Sublime和Github的内部结构的情况下，这是我能想到的最好的答案，除非Sublime是开源的，否则这是不会发生的事情(至少在Sublime的情况下)。祝好运!|2507947|entityMap|0|LINK|mutability|MUTABLE|url|https://sublime.wbond.net/packages/BracketHighlighter|1|https://github.com/github/linguist#syntax-highlighting^0|2A|7|3V|I|3V|I|0|77|8|1|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]|$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

So I've tested a bunch of languages in Sublime that have multiline comments (C/C++, Java, HTML, PHP, JavaScript), and none of the language syntaxes support multiline comments embedded in multiline comments - the syntax highlighting for the <code>comment</code> scope ends with the first "comment close" marker, not with symmetric markers. Now, this isn't to say that it's impossible, because the <a href="https://sublime.wbond.net/packages/BracketHighlighter" rel="nofollow"><code>BracketHighlighter</code></a> plugin works great for matching symmetric tags, brackets, and other markers. However, it's written in Python, and uses custom logic for its matching algorithms, something that may not be available in the Oniguruma engine that powers Sublime's syntax highlighter, and apparently <a href="https://github.com/github/linguist#syntax-highlighting" rel="nofollow">Github's</a> as well.

Basically, from your description of the problem, you need a code parser to ensure that nested comments are legal, something you can't do with just a syntax highlighting definition. If you're writing this just for Sublime, a custom plugin could take care of that, but I don't know enough about Github's Linguist syntax highlighting system to say if you're allowed to do that. I'm not a regex master yet, but it seems to me that it would be rather difficult to achieve this purely by regex, as you'd need to somehow keep track of an arbitrary number of internal symmetric "open" and "close" markers before finding (and identifying!) the final one.

Sorry I couldn't provide a definitive answer other than I'm not sure this is possible, but that's the best I can come up with without knowing more about Sublime's and Github's internals, something that (at least in Sublime's case) won't happen unless it's open-sourced. Good luck!

blocks|key|2507949|text|您的想法是正确的，但是看起来您的第二个模式也匹配"begin+nested+comment“序列#%7C，它永远不会给您的递归#multilinecomment模式提供发挥作用的机会。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2507950|您所要做的就是将第二个模式替换为类似于|2507951|(#(?=[%5E%7C])%7C\%7C(?=[%5E#])%7C[%5E%7C#])%2B|code-block|syntax|javascript|2507952|entityMap^0|1C|2|1P|H|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

You had the correct idea but it looks like your second pattern also matches for the "begin nested comment" sequence <code>#|</code> which will never give a chance for your recursive <code>#multilinecomment</code> pattern to kick in.

All you have to do is replace your second pattern with something similar to

<pre><code>(#(?=[^|])|\|(?=[^#])|[^|#])+
</code></pre>

blocks|key|2718438|text|旧帖子，我没有评论的名声，但绝对不可能使用纯粹的正则表达式来检测任意嵌套的评论。直观地说，这是因为所有正则表达式都可以转换为有限的状态机，并且跟踪嵌套深度需要(理论上)无限数量的状态(状态的数量至少需要等于不同的可能嵌套深度，这里是无限的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2718439|在实践中，这个数字增长非常慢，所以如果你不想太麻烦，你可以写一些东西，允许嵌套到合理的深度。否则，您可能需要一个单独的阶段来解析并找到注释，以告诉语法高亮工具忽略它们。|2718440|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Old post, and I don't have the reputation for a comment, but it is emphatically NOT possible to detect arbitrarily nested comments using purely regular expressions. Intuitively, this is because all regular expressions can be transformed into a finite state machine, and keeping track of nesting depth requires a (theoretically) infinite amount of state (the number of states needs to be equal to at least the different possible nesting depths, which here is infinite).

In practice this number grows very slowly, so if you don't want to go to too much trouble you could probably write something that allows nesting up to a reasonable depth. Otherwise you'll probably need a separate phase that parses through and finds the comments to tell the syntax highlighter to ignore them.

blocks|key|2508001|text|把最后一个match拿出来。你不需要它。它对于textmate自然要做的事情来说是多余的，那就是将所有额外的文本匹配到comment作用域中，直到结束标记出现，否则整个模式就会自己递归。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2508002|entityMap^0|5|5|1N|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Take the last <code>match</code> out. You do not need it. Its redundant to what textmate will do naturally, which is to match all additional text in to the <code>comment</code> scope until the end marker comes along, or the entire pattern recurses upon itself.

While writing a grammar for Github for syntax highlighting programs written in the Racket language, I have stumbled upon a problem.

In Racket <code>#|</code> starts a multiline comment and <code>|#</code> ends it.

The problem is that multiline comments can be nested:

<pre><code> #| a comment #| still a comment |# even 
 more comment |#
</code></pre>

Here is my non-working attempt:

<pre><code>repository:
 multilinecomment: 
 begin: \#\|
 end: \|\#
 name: comment
 contentName: comment
 patterns:
 - include: "#multilinecomment"
 name: comment
 - match: ([^\|]|\|(?=[^#]))*
 name: comment
</code></pre>

The intent of the match patterns are:

<ol>
<li><code>"#multilinecomment"</code>
 A multiline comment can contain another multiline comment.</li>
<li><code>([^\|]|\|(?=[^#]))*</code>
The meaning of the subexpressions:

<pre><code> [^\|] any characters not an `|`
 \|(?=[^#]) an `|` followed by a non-`#`
</code></pre></li>
</ol>

The entire expression thus matches a string not containg |#

Update:

Got an answer from Allan Odgaard on the TextMate mailing list:

<a href="http://textmate.1073791.n5.nabble.com/TextMate-grammars-and-nested-multiline-comments-td28743.html" rel="nofollow">http://textmate.1073791.n5.nabble.com/TextMate-grammars-and-nested-multiline-comments-td28743.html</a>

Matching nested constructs in TextMate / Sublime Text / Atom language grammars

Python

Java

问匹配TextMate / Sublime Text / Atom语言语法中的嵌套构造
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问匹配TextMate / Sublime Text / Atom语言语法中的嵌套构造EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问匹配TextMate / Sublime Text / Atom语言语法中的嵌套构造
EN