-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide possibility to use existing Asciidoctor Instance instead embedded variant. #147
Comments
- removed unnecessary dependency to OSGI wrapper from editor - implemented speciall asciidoctor implementation which just uses installed variant - preferences added + defaults
before you finish up working on it, would it be possible to have the option to give a path to the asciidoctor executable? |
Okay, will implement. so reopen issue |
@sjaeckel Is now configurable: |
@sjaeckel just released version 1.2.0 on marketplace |
- removed unnecessary dependency to OSGI wrapper from editor - implemented speciall asciidoctor implementation which just uses installed variant - preferences added + defaults
- supporting now syntax highlighting at console - exit code>0 output will be shown as script error in editor + problem view - improved console handling + behaviour (e.g. own factory, so found in console list)
Wanted
There shall be the possiblity to use an existing asciidoctor installation instead of embedded variant.
This will solve #136 , #69 and also #116 .
The implementation will do a CLI call. This is for advanced users having their own working asciidoctor instance with custom templates, extensions etc.
How to implement
This will be a full CLI call as done on console .
Optional
Having no embedded JRuby the cli call could show the asciidoc outputso in a dedicated console.
Remarks
Maybe parts of EGradle CLI handling could be copied and adapted...
The text was updated successfully, but these errors were encountered: