Skip to content

The problem of leaking incorrect RST markup #1

@mettta

Description

@mettta

An invalid included RST markup breaks further markup of the file by exceeding the scope and eating at least one end-of-scope marker. In the file tmLanguage (plist) it was possible to capture the scope with RST content more clearly, and the RST text does not leak to the limits of the scope (tested in TextMate).
Using this method in JSON does not work.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions