atom-language-asciidoc
atom-language-asciidoc copied to clipboard
⚛ AsciiDoc language package for the Atom editor.
## Description The regex for the quote-paragraph rule is not as robust as it could be -- and also, either not as efficient as it could be, or else (if...
[Enter steps to reproduce:] 1. ... 2. ... **Atom**: 1.57.0 x64 **Electron**: 9.4.4 **OS**: Unknown Windows version **Thrown From**: [language-asciidoc](https://github.com/asciidoctor/atom-language-asciidoc) package 1.11.0 ### Stack Trace Failed to activate the language-asciidoc...
## Description A footnote with an id (see https://asciidoctor.org/docs/user-manual/#user-footnotes) is not highlighted . ## Screenshots   ## Syntax example ```adoc The hail-and-rainbow protocol can be initiated at five levels:...
## Description If an include macro is used within a pass-through block with the macros substitution enabled, the syntax highlighter will not finish correctly and the remainder of the document...
## Description Inline stem escaping sequence `\]` as `]` is not correctly highlighted in [email protected]. https://asciidoctor.org/docs/user-manual/#stem-in ## Screenshots   ## Syntax...
Usually neither attribute definitions, e.g. ``` :imagesdir: figures ``` nor attribute usages, e.g. ``` {doctitle} ``` constitute proper words. Same goes for macros that are often interpreted as a single...
From [9.5 section of the manual](https://asciidoctor.org/docs/user-manual/#escaping-unconstrained-quotes):  Currenty, highlighting will be breaked if you try to use asterisk instead of word "TEXT": ``` *Here is bold text about...
## Description I was writing code snippets in an AsciiDoc document using the bash syntax highlighter, and I noticed that the highlighting was leaking outside the `[source,bash]` block. This is...
## Description A space character is permitted after the term (but before the delimiter) in a description list. However, if a space is present at this position, the term is...
## Description Atom master recently landed support for a new parser: atom/atom#16299 We need to investigate on this new parser.