AsciiDoc support for Visual Studio Code

An extension that provides live preview, syntax highlighting and snippets for the AsciiDoc format using Asciidoctor.

How to Install

Launch Visual Studio Code "Quick Open" (Ctrl+P), paste the following command, and press Enter:

ext install asciidoctor.asciidoctor-vscode

Alternatively, you can use the built-in extension browser to find the AsciiDoc by asciidoctor extension and install it.

This extension is also available as a pre-version (alpha) in Visual Studio Code for the Web and can be installed using the same procedure.

How to Use

The extension activates automatically when opening an AsciiDoc file (.adoc, .ad, .asc, .asciidoc).

Preview

To show the preview you can use the same commands as the Markdown extension:

• Toggle Preview - ctrl+shift+v (Mac: cmd+shift+v)
• Open Preview to the Side - ctrl+k v (Mac: cmd+k v)

The extension updates automatically the preview but it can also be forced with the AsciiDoc: Refresh Preview command.

The preview supports setting AsciiDoc attributes through the asciidoc.preview.asciidoctorAttributes setting.

By default, the preview uses VS Code editor theme (workbench.colorTheme). To use Asciidoctor default style set the asciidoc.preview.useEditorStyle setting to false. It is possible to set your own preview stylesheet with the asciidoc.preview.style setting.
It is also possible to define custom templates with the asciidoc.preview.templates setting.
(See more details under Extension Settings)

Export as PDF

The extension provides a quick command to export your AsciiDoc file as PDF.

• Open the command palette - ctrl+shift+p or F1 (Mac: cmd+shift+p)
• Select AsciiDoc: Export document as PDF
• Choose the folder and filename for the generated PDF

By default, the PDF export feature relies on asciidoctor-pdf. If you prefer to use wkhtmltopdf, set the asciidoc.pdf.engine setting to wkhtmltopdf and configure the asciidoc.pdf.wkhtmltopdfCommandPath if necessary.
(See more details under Extension Settings)

Save as HTML

The extension provides a quick command to export your AsciiDoc file as HTML using the default Asciidoctor stylesheet.

• Open the command palette - ctrl+shift+p or F1 (Mac: cmd+shift+p)
• Select AsciiDoc: Save HTML document
• The file is generated in the same folder as the source document

The shortcut key of ctrl+alt+s (Mac: cmd+alt+s) will also save the document.

Save to Docbook

The extension provides a quick command to export your AsciiDoc file as DocBook.

• Open the command palette - ctrl+shift+p or F1 (Mac: cmd+shift+p)
• Select AsciiDoc: Save to DocBook
• The file is generated in the same folder as the source document

ℹ️ Note: Only DocBook 5 is supported.

Snippets

Several code snippets are provided including but not limited to: include statements, images, links, header, headings, lists, blocks, etc...

For a full list open the command palette and select Insert Snippet.

Identifying the VS Code Environment

The env-vscode attribute is set on all output documents. If you need to identify or handle the VS Code environment you can use an ifdef expression similar to the following:

ifdef::env-vscode[]
This is for vscode only
endif::[]

Diagram Integration

This extension supports a wide range of diagrams from BPMN to Graphviz to PlantUML and Vega graphs using Kroki and asciidoctor-kroki.

You can see the full range on the Kroki website.

Note that this extension will send graph information to https://kroki.io. If this is an issue it is also possible to use your own Kroki instance (see the instructions for further information).

To enable diagram support, set the asciidoc.extensions.enableKroki setting to true.

❗ Important: Please note that :kroki-fetch-diagram: is currently not supported because it relies on unxhr which does not work in VS Code (https://github.com/ggrossetie/unxhr/issues/98).

Use Asciidoctor.js extensions

When using the preview, the VS Code extension can load and register Asciidoctor.js extensions.

By convention, extensions must be located in .asciidoctor/lib (at the root of your workspace). The VS Code extension will recursively load all files with the extension .js as Asciidoctor.js extensions. For instance, the following files will be loaded: .asciidoctor/lib/emoji.js, .asciidoctor/lib/emoji/index.js and .asciidoctor/lib/foo/bar/baz.js.

To use an Asciidoctor.js extension, you should enable the feature by checking "Enable Asciidoctor.js extensions registration" in the extension settings. The first time, you will also need to confirm that you trust the authors of the Asciidoctor.js extensions located in .asciidoctor/lib.

❗ Important: This feature will execute JavaScript code and should not be enabled if you don't fully trust the authors of the Asciidoctor.js extensions.

💡 Tip: You can always update the trust mode using the command "Manage Asciidoctor.js Extensions Trust Mode".

You can create a new extension by creating a JavaScript file in the .asciidoctor/lib directory or use an existing one. Here's an example of how to use the asciidoctor-emoji extension:

1. Install the npm package in the workspace directory:

   npm i asciidoctor-emoji
   

2. Create a file a JavaScript file in .asciidoctor/lib with the following content:

   module.exports = require('asciidoctor-emoji')
   

3. Enjoy :tada:

Asciidoctor Config File

To provide a common set of variables when rendering the preview, the extension reads an .asciidoctorconfig or .asciidoctorconfig.adoc configuration file. Use this to optimize the preview when the project contains a document that is split out to multiple include-files.

It is inspired by the implementation provided in IntelliJ AsciiDoc Plugin and reused in Eclipse AsciiDoc plugin.

Extension Settings

This extension contributes the following settings:

Preview

PDF

Extensions

General

Debug

Build and Install from Source

Manual

git clone https://github.com/asciidoctor/asciidoctor-vscode
cd asciidoctor-vscode
npm install
npm run package
code --install-extension *.vsix

Issues

If you encounter any problems with the extension and cannot find the solution yourself, please open an issue in the dedicated GitHub page: asciidoctor-vscode/issues.

Before opening an issue, please make sure that it is not a duplicate. Your problem may have already been brought up by another user and been solved: asciidoctor-vscode/issues all.

When you do open an issue, remember to include the following information:

1. Description of the issue
2. VSCode version, OS (Help -> About) and extension version
3. Steps to reproduce the issue
   IMPORTANT: We cannot solve the issue if you do not explain how you encountered it
4. If the problem occurs only with a specific file, attach it, together with any screenshot that might better show what the issue is.

If your issue only appeared after updating to a new version of the extension, you can roll back to a previous one via the extensions browser. Click on the small gear icon beside the AsciiDoc extension, then select Install Another Version.... A selection menu will appear allowing you to select which version you want to install.

Contributing

To contribute simply clone the repository and then commit your changes. When you do a pull request please clearly highlight what you changed in the pull comment.

Do not update the extension version or changelog, it will be done by the maintainers when a new version is released.

If you want to update the readme, you are free to fix typos, errors, and add or improve descriptions; but, if you have a style change in mind please use an issue (or specific pull request) so that it can be discussed.

Credits

• AsciiDoc by Stuart Rackham
• Asciidoctor organization for the language flavor
• Asciidoctor.js for the preview
• Asciidoctor PDF for the Export to PDF function
• wkhtmltopdf for the Export to PDF function
• Each and every contributor to this extension.