克隆一个突出显示语法定义的sublime文本3

Question

是否有一个简单的过程来从现有的自定义sublime文本3突出显示定义？

我AAAPackageDev按照有序且稍微繁琐的教程的建议安装了创建新的突出显示语法定义,但我发现克隆一个会让我走得更快.至少,我想学习如何浏览sublime附带的默认语法定义.

如果你真的想要完全具体,我希望完成的是一个原始的突出显示方案,其中给定的一对开始和结束标记之间的任何字符串,我自己的定义,将被着色.并且我自己定义的另一对不同标记之间的任何字符串都将以第二种颜色着色.一个好处就是让令牌本身变灰.

(Ubuntu 14.04)

谢谢!

Answer 1

更新2015-05-10:Sublime Text 3 build 3084引入了一种sublime-syntax用于编写语法定义的全新格式.它比Sublime继承自TextMate的旧系统要好得多.新系统应尽快登陆公众ST3测试版.由于ST3是Sublime的推荐版本,我建议使用新系统而不是下面描述的系统编写任何新的荧光笔.

这是Sublime Text语法高亮的速成课程.

建立

首先,正如@lthreed所指出的,您可以使用PackageResourceViewer查看Sublime Text附带的默认包.那些.tmLanguage文件都是plist格式,这是非常难以阅读和理解的.PackageDev可以将plist文件转换为更易读的JSON或YAML格式.当您通过查看默认包进行学习时,请务必先将其转换为YAML.请注意,PackageDev可能无法完美转换.没关系.您只是将代码用作参考.

plist是Sublime理解的原生格式,但这并不意味着你应该这样写.我强烈建议您在YAML中编写荧光笔并将其转换为带有的荧光笔PackageDev.不要用JSON写它.JSON不支持原始字符串.所有正则表达式都必须进行双重转义.这绝对是一场噩梦.只需使用YAML.

您可以通过打开命令调色板(cmd+shift+p在Mac上)并选择来启动新的语法定义PackageDev: New YAML Syntax Definition.当您准备测试它时,打开命令面板并选择PackageDev: Convert (YAML, JSON, PList) to...,PackageDev会发现您有一个YAML文件并想要转换为plist.转换将获取.YAML-tmLanguage文件并吐出Sublime理解的.tmLanguage文件.将该文件放在/ Packages/User目录中,Sublime将加载并应用它(您可能必须重新启动).

Sublime语法高亮显示的工作原理

您正在编写的语法定义不会直接为文本着色.它将范围名称应用于文本.然后,编写像Monokai和Solarized这样的主题的人会出现并创建将范围名称与颜色相关联的文件.您可以组成自己的范围名称,但是您应该坚持使用官方的TextMate范围名称.对于您匹配的代码,这些范围名称可能没有任何意义.没关系.尽你所能.如果必须组成范围名称,请使用TextMate范围名称作为起点.例如,代替string.quoted.double.xxx(其中xxx是您匹配的语言的文件扩展名),您可以组成一个名为的范围名称string.quoted.triple.xxx.

代码示例

这是一个带有文件扩展名.matt的哑光语言的语法定义.它只有两个规则:一个用于匹配管道分隔的字符串,另一个用于匹配字符串和更复杂的分隔符.

# [PackageDev] target_format: plist, ext: tmLanguage
---
name: Mattlang
scopeName: source.matt
fileTypes: [matt]

patterns:
- include: '#pipe-string'
- include: '#complex-string'

# Rules defined in the repository can reference each other. You can include
# one rule inside another.
repository:
  # This is a rule of the begin-end form. The rule matches a string bounded by
  # pipes, such as |hello there|
  pipe-string:
    # The optional 'name' field lets you apply a single scope to everything,
    # including the begin-end pipes. All the scope names must end with .matt
    name: everything.matt
    # We have to escape the pipe character, because it's a special character in
    # the Oniguruma regex syntax (and most other regex engines).
    begin: \|
    # 'beginCaptures' is required if you want the pipes to be colored differently
    beginCaptures:
      # In regex jargon, the begin pipe is 'captured'. Capture group 0 means the
      # entire match, which in this case is just the pipe.
      '0': {name: entire.begin.match.matt}
    # The optional 'contentName' field lets you apply a scope to all the text
    # between (but not including) the begin-end pipes.
    contentName: stuff.between.the.pipes.matt
    patterns:
    # These rules will only be applied to the text *BETWEEN* the pipes. Sublime
    # will go through the rules from top to bottom and try to match the text, so
    # higher rules have a higher "precedence" and will get matched first.
    # Given the text |hello there|, Sublime will see an 'h' character and move
    # through the rules from top to bottom trying to find a rule that starts
    # with 'h'. The #hell rule will match the 'h' and the rest of the
    # characters. The #hell scope name will be applied to the 'hell' text and 
    # Sublime will resume trying to find the next match at the 'o' character.
    # The 'o' character WILL NOT match #hello. You can think of the matched text
    # as being removed from the stream entirely. The point is: order matters.
    - include: '#hell'
    - include: '#hello'
    - end: \|
    endCaptures:
      '0': {name: entire.end.match.matt}

  # This is the other form of rule you can define. It's extremely simple --
  # just a scope name and a regex pattern to match. Note that these rules will
  # only match text on the same line, unlike begin-end rules, which can cover
  # multiple lines.
  hell:
    name: some.other.scope.matt
    match: hell

  hello:
    name: some.scope.matt
    match: hello

  # This rule matches a string that starts with $!! and ends with !!$,
  # e.g. !!$hello there!!$
  complex-string:
    # I've labeled the capture groups.
    #      |---0---|
    #      |--1-||3|
    begin: (!(!))($)
    #        |2|
    beginCaptures:
      '0': {name: full.match.matt}
      '1': {name: both.exclamation.marks.matt}
      '2': {name: second.exclamation.mark.matt}
      '3': {name: dollar.sign.matt}
    # It's ok to leave out the 'patterns' field. Technically, all you really
    # need is a 'begin' field and an 'end' field.
    end: ((!)!)($)
    endCaptures:
      '0': {name: everything.matt}
      '1': {name: both.exclamation.marks.matt}
      '2': {name: first.exclamation.mark.matt}
      '3': {name: dollar.sign.matt}

Answer 2

如果安装PackageResourceViewer,则可以打开任何内置的压缩​​资源.Do PackageResourceViewer:Open Resource,然后选择您熟悉的语言.然后选择扩展名为.tmLanguage的文件.