AsciiDoc is a text document format for writing short documents, articles, books and UNIX man pages. AsciiDoc files can be translated to HTML and DocBook markups.
adoc-mode is an Emacs major mode for editing AsciiDoc files. It emphasizes
the idea that the document is highlighted so it pretty much looks like the
final output. What must be bold is bold, what must be italic is italic etc.
Meta characters are naturally still visible, but in a faint way, so they can
be easily ignored.
Here are some of the main features of adoc-mode:
-
comprehensive syntax highlighting for all AsciiDoc elements
-
native fontification of source code blocks using language-appropriate major modes
-
font-lock support for Asciidoctor inline macros (
]+btn:[,menu:[], etc.) -
inline image preview with right-click context menus and remote image support
-
~50 tempo templates for inserting AsciiDoc markup (formatting, titles, blocks, lists, macros, etc.)
-
title management: promote / demote, toggle between one-line and two-line styles, adjust underline length
-
navigate to anchors (
C-c C-a) and follow URLs,include::macros, and xrefs at point (C-c C-o/M-.) -
nested
imenuindex with hierarchical heading structure -
support for
outline-mode(one-line title style only) -
integration with
flyspell-mode(skips non-prose regions), comment commands (M-;), and compilation mode
If you’re looking for a lighter-weight alternative, check out asciidoc-mode — a tree-sitter-based AsciiDoc mode focused on the essentials (highlighting, navigation, folding). It requires Emacs 30.1+ and trades `adoc-mode’s richer feature set for simplicity and the performance benefits of tree-sitter. Both modes are maintained by the same author.
adoc-mode is available on NonGNU ELPA (Emacs 28+),
MELPA Stable and MELPA.
NonGNU ELPA is enabled by default in Emacs 28+, so adoc-mode can be installed
without any additional package archive configuration. MELPA Stable carries
the latest stable version, while MELPA has a development snapshot for users
who don’t mind breakage but don’t want to run adoc-mode from a git checkout.
You can install adoc-mode using the following command:
M-x package-install RET adoc-mode RET
If the installation doesn’t work try refreshing the package list:
M-x package-refresh-contents
Alternatively, you can add something like this to your Emacs config:
(unless (package-installed-p 'adoc-mode)
(package-refresh-contents)
(package-install 'adoc-mode))or if you’re into use-package:
(use-package adoc-mode
:ensure t)Adoc-mode is designed for intuitive use. Most features are available from the AsciiDoc menu in the menu bar.
This section only describes some not so obvious features.
If you click mouse-3 on an image link like
image:path/to/image[] the Image context menu pops up.
This context menu allows you to generate or remove the preview for the linked image.
The menu item AsciiDoc → Toggle display of images runs the command
adoc-toggle-images. It removes all image previews from the buffer
if there are any. If there are no image previews in the buffer it
generates them for all image links.
This may be confusing if all image previews are outside the visible
region of the buffer. In this case, you might expect adoc-toggle-images
to generate the previews for the image links in the visible area on
the first run. But it does not, since it first removes all the
previews, even if you have not seen them.
Just run adoc-toggle-images again if it does not do what you expect on
the first run.
The .adoc and .asciidoc file extensions are associated with adoc-mode automatically.
|
Note
|
An old AsciiDoc manual lists .txt as the standard extension. If you want adoc-mode for .txt files as well, add this to your init file:
|
(add-to-list 'auto-mode-alist (cons "\\.txt\\'" 'adoc-mode))You can see a list of all configuration options offered by adoc-mode by running the following command - M-x customize-group adoc.
Out-of-the-box adoc-mode will try to apply native font-locking to source code blocks (e.g. the same font-locking that ruby-mode would use for Ruby code blocks).
This can be tweaked by several configuration options:
-
Native fontification of source blocks can be switched off by setting
adoc-fontify-code-blocks-nativelytonil. The default value is5000, meaning only code blocks of 5000 characters or fewer are fontified natively. -
Native fontification of lengthy code blocks can cause performance problems. If the value of
adoc-fontify-code-blocks-nativelyis an integer only those code blocks are fontified natively whose length is less or equal to that value. Set it totto fontify all code blocks regardless of size. -
To avoid performance problems with code block beginnings that do not have a matching end yet the scanning for the code block end is delimited by
adoc-font-lock-extend-after-change-max. -
All programming languages
XYZthat have an Emacs major modeXYZ-modeand usefont-lockare automatically supported. Some other languages not fitting into that name scheme are supported through the alistadoc-code-lang-modes. You can add your own languages and modes there if they work based onfont-lockand are not automatically supported. -
The fall-back language mode is
prog-modewithout any fontification. You can set your own default byadoc-fontify-code-block-default-mode.
Images are shown as preview by default when you open an AsciiDoc file.
You can avoid this by deactivating the option adoc-display-images.
(setq adoc-display-images nil)By default, images are displayed at their actual size. You can limit the maximum dimensions by setting adoc-max-image-size to a cons cell of (MAX-WIDTH . MAX-HEIGHT) in pixels:
(setq adoc-max-image-size '(640 . 480))|
Note
|
Image resizing requires Emacs to be built with ImageMagick support. |
An image link can also be given as url to a remote image. The display of remote images is switched off by default. You can activate it by the option adoc-display-remote-images.
(setq adoc-display-remote-images t)Images are only downloaded if the protocol of the url matches one of those in the list adoc-remote-image-protocols. This list can be customized. By default, it only contains the entry https.
It is possible to customize the way adoc-mode renders different text
elements (faces) like section titles, text or punctuation styles. For
example, if you would like a level 1 section title to have a different
text color or height you can achieve this by using standard Emacs
functionality.
First of all, list all available faces by running
M-x list-faces-display
and searching for lines with the adoc- prefix.
Alternatively, you can get information about the face under point by calling
M-x describe-face
One possible solution to change the look of a face is to use the
built-in use-package feature :custom-face.
Example:
(use-package adoc-mode
:ensure t
:custom-face
(adoc-title-0-face ((t (:height 1.0 :weight bold)))))Of course, this is only one way to do it. Emacs has a few ways to customize faces. Simply, pick the one you prefer.
If your default face is a fixed pitch (monospace) face, but in AsciiDoc files
you’d like to have normal text with a variable pitch face, variable-pitch-mode
is a good option:
(add-hook 'adoc-mode-hook #'variable-pitch-mode)adoc-mode was created by Florian Kaufmann in 2009. Eventually the development
was halted in 2016 and the mode was dormant for the next 6 years. In 2022
Tobias Zawada encouraged the Emacs community to revive the development and after a brief period under the Emacs Orphanage org, Bozhidar Batsov assumed the project’s maintenance.
These days all upstream packages (e.g. on MELPA) are built from Bozhidar’s fork.
Here are some features that we’re considering to add in the future:
-
Demote / promote for list items
-
Correctly highlighting backslash escapes
Check out the issue tracker for more details.
adoc-mode uses Eldev for development, so you should install the tool first.
The easiest and "purest" way to run adoc-mode is to execute:
$ eldev emacs
This will start a separate Emacs process with adoc-mode and its
dependencies available, but without your normal packages installed.
However, you can use Eldev-local to add some packages with
(eldev-add-extra-dependencies 'emacs …) forms. See Eldev
documentation for details.
Alternatively, if you want to load adoc-mode from source code in the Emacs you use for editing:
-
Generate autoloads file (that’s done automatically when installing via
package.elbut you’ll have to do it manually in this case):
$ eldev build :autoloads-
Add to your
.emacs:
;; load adoc-mode from its source code
(add-to-list 'load-path "~/projects/adoc-mode")
(load "adoc-mode-autoloads" t t)It’s perfectly fine to load adoc-mode from package.el and then to start making
experiments by changing existing code and adding new code.
A very good workflow is to just open the source code you’ve cloned and start
evaluating the code you’ve altered/added with commands like C-M-x,
eval-buffer and so on.
Once you’ve evaluated the new code, you can invoke some interactive command that
uses it internally or open an Emacs Lisp REPL and experiment with it there. You
can open an Emacs Lisp REPL with M-x ielm.
You can also quickly evaluate some Emacs Lisp code in the minibuffer with M-:.
Run all tests with:
$ eldev test|
Note
|
Tests may not run correctly inside Emacs' shell-mode buffers. Running
them in a terminal is recommended.
|
You can also check for compliance with a variety of coding standards in batch mode (including docstrings):
$ eldev lintTo check for byte-compilation warnings you can just compile the project with Eldev:
$ eldev compileCopyright © 2009-2016 Florian Kaufmann
Copyright © 2022-2026 Bozhidar Batsov and adoc-mode contributors
Distributed under the GNU General Public License; type C-h C-c to view it.
