Fix hanging indents for admonition (eg NOTE) blocks#41
Fix hanging indents for admonition (eg NOTE) blocks#41hjwp wants to merge 1 commit intocathaysia:masterfrom
Conversation
|
PS - looking at the asciidoc documentation, maybe hanging indents like this aren't explicitly part of the spec? https://docs.asciidoctor.org/asciidoc/latest/blocks/admonitions/ it's certainly how i've always written them, i find it easier to visually see my NOTE blocks stand out. but i'll understand if you want to say the spec is unclear on this, and you want to put it out of scope. |
|
otoh both legacy |
|
Maybe a related issue: When a list item spans multiple lines, the lines after the first one are also highlighted: |
|
The problem with this bug is that the parser only considers admonition as one line. But asciidoctor requires two consecutive NEW_LINE or EOF. @bonusnunc list item also has the similar problem. |
There are always welcome. But please follow this specification for git commit message: |
|
Hi, I changed the commit message, lmk if that now follows the conventions you prefer? it's only the test so far I'm afraid! I don't feel qualified to attempt the actual fix 😅 |

Hi there, not sure if bug reports / suggestions are welcome, but I noticed some strange highlighting for "hanging indented" blocks. I noticed it with
NOTE:admonitions, but it also happens for<1> callouts. example:highlights as:
looking at
InspectTree, i think it's recognising the second line as being a separate block?In an attempt to be hepful, I've tried to add an example in the tests corpus, with my non-expert best guess as to what the tree should be?