You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to expose the line numbers to the end user for errors (and warnings as well)?
I submitted the issue #1608 a while ago and, while understanding that this is the expected behaviour, it nevertheless makes it difficult for the end user (me in this case) to understand where the offending asciidoc source is.
My use case is that we have large (+200 pages) technical docs with many tables. The stack trace emitted for issue #1608 will not help much when it comes to finding the offending table.
After poking around in the code a bit, it seems that there is a 'sourcemap' option usable from the API that is not set by the asciidoctor-pdf cli invokation (for performance reasons??). If I understand the code correctly it is not possible to set this from the user's perspective using the cli.
To solve my particular problem, I made a short proof-of-concept to expose the line numbers for the case of issue #1608 in
Would it be possible to expose the line numbers to the end user for errors (and warnings as well)?
I submitted the issue #1608 a while ago and, while understanding that this is the expected behaviour, it nevertheless makes it difficult for the end user (me in this case) to understand where the offending asciidoc source is.
My use case is that we have large (+200 pages) technical docs with many tables. The stack trace emitted for issue #1608 will not help much when it comes to finding the offending table.
After poking around in the code a bit, it seems that there is a 'sourcemap' option usable from the API that is not set by the asciidoctor-pdf cli invokation (for performance reasons??). If I understand the code correctly it is not possible to set this from the user's perspective using the cli.
To solve my particular problem, I made a short proof-of-concept to expose the line numbers for the case of issue #1608 in
https://github.com/rillbert/asciidoctor-pdf/tree/personal/rillbert/report_line_at_cannotfit
but as you can see it is neither very generic or pretty. I also patched asciidoctor cli to set the sourcemap option to true.
So, do I miss some other way of accomplishing what I want with the current versions or is a generic solution out-of-scope for now?
The text was updated successfully, but these errors were encountered: