-
Notifications
You must be signed in to change notification settings - Fork 98
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Hopefully fixs regression with use_asciidoctor_js='False'- Thanks to @…
…danyill for the test'
- Loading branch information
João Pinto
committed
Mar 26, 2018
1 parent
9f04dad
commit 43faf6e
Showing
2 changed files
with
3 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43faf6e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry @joaompinto I'm not able to get output in this case and I can't see why.
Running a command in a shell with the same parameters works nicely:
asciidoctor -o- - -B /some/path < README.adoc
No output in the VS code developer tools. I tried to add a
console.log
statement in the extension code but it did not turn up in the developer tools (and I can't remember how to do it and my google fu is failing)I think there's a path resolution issue with
path.dirname(doc.fileName)
which seems to work for some paths but not others. So I am sporadically getting output depending on /some/path.In particular the path:
/home/test.adoc
works nicelyA longer path (but without spaces) is breaking:
/media/veracrypt51/Education/Gitlab/Synchrophasor_Sync_Check_Settings
When I look at the VS code source, there is no document, but the path appears correct in the
<base href=
element. So I'm a bit stuck for now. More later!43faf6e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danyill just opening the source with VS code, and then starting in debug (F5) should be sufficient for the console.log, please note that the output is only shown in the primary vscode instance "DEBUG CONSOLE" window, and not in the one running the extension.
Meanwhile I have set the current work directory on spawn(), 7448ab5 , this will have effect if doc.fileName is relative or absolute depending on the way you open a file/folder (just guessing, not sure it makes really a difference).