question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect "AsciiDoc old style heading" warning

See original GitHub issue

Consider the following example:

1. one
+
to
+
2. two

invalid

If I replace to to two (no pun intended) then the issue is gone 🤔

AsciiDoc Plugin Version 0.30.78

IDE Name and Version

IntelliJ IDEA 2019.3.5 (Ultimate Edition)
Build #IU-193.7288.26, built on May 6, 2020
Licensed to Guillaume GROSSETIE
You have a perpetual fallback license for this version
Subscription is active until November 27, 2020
Runtime version: 11.0.6+8-b520.66 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-106-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 4029M
Cores: 8
Registry: 
Non-Bundled Plugins: BashSupport, Batch Scripts Support, CMD Support, CheckStyle-IDEA, FindBugs-IDEA, JFormDesigner, com.dmarcotte.handlebars, com.intellij.ideolog, com.jetbrains.lang.ejs, com.jetbrains.plugins.jade, com.wix.eslint, org.asciidoctor.intellij.asciidoc, org.intellij.scala, org.jetbrains.idea.grammar, org.jetbrains.kotlin, org.jetbrains.plugins.slim, org.jetbrains.plugins.ruby

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
ahus1commented, Jun 28, 2020

There is now release 0.31.8 (for IntelliJ 2020.2 EAP) and pre-release 0.30.82 (for releases before IntelliJ 2020.1 and before) that should fix this.

It contains several refactorings and new test cases to handle contexts in lists better than before. There should be less false positive recognized enumerations due to this.

If you see regressions in the editor highlighting and/or re-formatting, please let me know and I’ll re-open this issue.

1reaction
ahus1commented, Jun 11, 2020

There is now a pre-release 0.30.79 that fixes this issue. Please give it a try.

The pre-release of the plugin is available from GitHub releases and the IntelliJ AsciiDoc EAP repository.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors and Warnings | Asciidoctor Docs
Errors do not stop conversion, but the output document will almost certainly be wrong. FATAL (FAILED). Failures are fatal; no output document will...
Read more >
Suppress certain warnings (asciidoc) · Issue #1164 - GitHub
Is it possible to suppress certain warnings? E.g. in asciidoc-format I make us of passthrough blocks to custom-define format attributes.
Read more >
AsciiDoc Syntax Quick Reference | Asciidoctor
The header may not contain blank lines and must be offset from the content by at least one blank line. Title only. =...
Read more >
Hugo Server Shouldn't Break on WARNINGs, only ERRORs
Hugo needs to distinguish between a WARNING coming back from the asciidoc parser and an ERROR and not to abandon site building on...
Read more >
AsciiDoc cheatsheet - Powerman
This is a cheatsheet for AsciiDoc - “Text based document generation” script. ... (because of some markup syntax changes) and using different css...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found