YAML scanner fails on objects in lists

[profmaad]

As seen in this ray: http://coderay.rubychan.de/rays/7788
the YAML scanner misinterprets the first key in an object stored in a list.

It interprets the entire first line (a: 1) as string/content, in every following line in the object, he correctly parses key: string/content.

[korny]

It's true, the YAML parser is very stupid. It successfully highlights simple files, but when you start to combine maps, lists etc., it breaks down.

The problem is already documented in #84. Is it okay to close this as a duplicate?

[profmaad]

Sure.
Is there any information when this might be fixed?

[korny]

Actually, I'm not sure it's possible. YAML is a very complex format (and possibly insecure, see CVE-2013-0156), so I would not dare to parse it or use Ruby's YAML parser(s). The scanner needs to stay a lexical scanner, trying to mimic the understanding of YAML structure through heuristics. We should improve these heuristics, but we will not reach a quality where everything works.

It's great to start collecting example code that produces unacceptable results; this is most helpful at the moment.

[korny]

Marked as duplicate, pending fix in #84.