1. 10 Sep, 2019 3 commits
  2. 05 Sep, 2019 2 commits
  3. 04 Sep, 2019 4 commits
  4. 03 Sep, 2019 1 commit
  5. 26 Aug, 2019 1 commit
  6. 15 Aug, 2019 1 commit
  7. 06 Aug, 2019 2 commits
  8. 05 Aug, 2019 1 commit
  9. 04 Aug, 2019 3 commits
  10. 03 Aug, 2019 1 commit
  11. 29 Jul, 2019 1 commit
  12. 22 Jul, 2019 2 commits
  13. 12 Jul, 2019 1 commit
  14. 22 Jun, 2019 1 commit
  15. 31 May, 2019 1 commit
  16. 29 May, 2019 4 commits
  17. 08 May, 2019 1 commit
  18. 29 Apr, 2019 6 commits
    • Christian Hergert's avatar
      tests: add example yaml file · 61ff68f6
      Christian Hergert authored
      This includes a couple snippets from the spec, to simplify testing.
      61ff68f6
    • Роман Донченко's avatar
      yaml.lang: improve the highlighting of quoted strings · a9c777c9
      Роман Донченко authored
      * Allow them to be multiline.
      
      * Add highlighting for escape sequences. This necessitates splitting
        the "string" context into "single-quoted-string" and
        "double-quoted-string", as the escaping rules are different.
      
      * Allow empty quoted strings ("") to be highlighted correctly. The previous
        end regex prevented the closing quote in this case to be recognized
        as such, as it required it to be preceded by at least one character.
      a9c777c9
    • Роман Донченко's avatar
      yaml.lang: fix some cases of falsely recognized map keys · d53e1abb
      Роман Донченко authored
      First, don't recognize keys inside of quoted strings. Currently, "a: b"
      is recognized as a map entry with `"a` as the key and `b"` as the value.
      Fix that by giving the "string" context a higher priority than the "map"
      context.
      
      Second, prevent some comments from being recognized as map entries.
      Specifically, cases like this:
      
       # foo: bar
      
      Even though the "map" context has lower priority than the "comment"
      context, this would still be recognized as a map entry, because the map
      regex would match the line starting with the leading space and thus be
      the leftmost match. Fix this by requiring the first character of a map
      key to not be a whitespace character.
      
      There is still a case where a map entry is recognized where it shouldn't
      be:
      
      foo # bar: baz
      
      However, I don't see a way to fix this without running into the
      performance problem described in the comment in the "map" context
      definition.
      d53e1abb
    • Роман Донченко's avatar
      yaml.lang: improve detection of block scalars · eda6cda0
      Роман Донченко authored
      Allow chomping indicators, indentation indicators, trailing whitespace
      and a trailing comment on the line with the block scalar indicator.
      See the YAML 1.2 spec, section 8.1.1.
      
      Unfortunately, we can't use the indentation indicator to determine which of
      the following lines to include in the scalar, so a block scalar with an
      indentation indicator will still be highlighted incorrectly overall, unless the
      indicator is redundant.
      eda6cda0
    • Christian Hergert's avatar
      30886111
    • Jordi Mas's avatar
      build: update build instructions · 0cf0a283
      Jordi Mas authored
      0cf0a283
  19. 28 Apr, 2019 1 commit
  20. 27 Apr, 2019 2 commits
  21. 26 Apr, 2019 1 commit