Support for working with the HOL4 interactive theorem prover in Visual Studio Code. This plugin provides the required functionality to maintain a HOL session in an editor window, basic syntax highlighting, and basic unicode input completion. Everything else — diagnostics, hover, go-to-definition, the outline, symbol search and completion — comes from the HOL language server; see below.
Expects a HOL4 installation to exist, and the environment variable $HOLDIR to point to this
installation. The HOL4 homepage can be found here and its GitHub
repository here.
When hol4-mode.lsp.enabled is true (the default), the extension
starts a HOL4 Language Server Protocol
client that speaks to bin/hol lsp. This delivers:
- Compile-driven diagnostics in the Problems panel and inline squiggles as you edit.
- Hover with type information from the running HOL session, and a theorem's statement when the cursor is on one.
- Outline, symbol search and completion —
Ctrl+Shift+Ofor a file's declarations,Ctrl+Tto search stored theorems, and completion of names in scope. Symbol search covers the theories this script loads and, beyond them, any theory built in the project: those are marked not an ancestor, since using one means adding it toAncestorsfirst. - HOL Goals side pane — press
Ctrl+H Ctrl+G(orCmd+H Cmd+Gon macOS) to open a pane that follows the cursor and shows the proof state at each tactic step inside aProof … QEDblock.
The server picks its LSP position encoding from what this client
advertises, which is utf-16 — so hover, go-to-definition and the
squiggles in the Problems panel land on the right characters even on
lines carrying ∀, ⇒ or ‘…’, which used to be off by the
difference between bytes and code units. Nothing in the extension
translates positions any more.
The Goals pane measures its own width and tells the server, so HOL's pretty printer breaks lines to fit the pane you actually have rather than a fixed 75 columns. Resizing the pane re-renders at the new width.
The server refuses to compile a script that names a theory or library
it cannot load — one that has not been built yet, or that raises on
load. With an ancestor missing there is nothing to elaborate the file
against, so every name the file takes from that ancestor would draw
its own error; instead you get one diagnostic, on the Ancestors /
Libs entry that named the missing module, and nothing else in the
file is compiled. The status bar reads HOL LSP: not compiling and
the Goals pane says why rather than reporting "no goal state at this
position".
Build the missing dependency with Holmake, then edit the file's
Ancestors / Libs header — any change to that list, including a
change and its undo — and the server tries again. If the header is
already right, HOL: Compile the active script again retries without
touching the file.
A bin/hol lsp process can serve exactly one theory script for its
lifetime. Loading a script's ancestors puts them in the theory graph
and seals them, and the seal is a process-global soundness gate
against cross-theory redefinition: a second script's ancestors can
then be neither re-read nor withdrawn. A shared server does not fail
loudly, it answers with wrong goal states and dead hovers.
So the extension starts one server per *Script.sml file, when that
file first becomes visible, and stops it when the file is closed.
Each server runs in its script's own directory, so it picks up the
Holmakefile (and any HOLHEAP) that governs that script.
Two consequences worth knowing:
- Each server loads a HOL heap, which costs a few seconds and a few hundred megabytes. Opening ten scripts at once starts ten of them.
.sigfiles and non-script.smlfiles get no server. They declare no theory of their own, so there is no goal state to show.
Requirements: a HOL4 build recent enough that bin/hol lsp is a
valid subcommand. See tools-poly/lsp/README.md
in the HOL4 repository for the server contract.
Related settings:
hol4-mode.lsp.enabled(default:true) — toggle the client entirely. Withfalsethe extension behaves as it did before the LSP integration.hol4-mode.lsp.executable(default: empty) — override the path tobin/hol. Falls back tohol4-mode.holdir/bin/hol, then$HOLDIR/bin/hol.
Palette commands: HOL: Toggle HOL Goals pane, HOL: Restart LSP server for the active script, HOL: Show LSP output channel for the active script, HOL: Compile the active script again. All but the
first, and the status bar item, act on the server belonging to the
script in the active editor.
There is no longer a hol4-mode.indexing setting. The symbol
indexer it governed has been removed: the language server answers the
same requests from HOL itself rather than from a regex scan of the
sources, so there is one implementation and it is the one that knows
what the names mean. Any .hol-vscode directory left in a workspace
(or in $HOLDIR) is now unused and can be deleted.
Suggested additions to settings.json for use with VSCodeVim,
somewhat corresponding to the HOL4 Vim mode defaults:
{
"vim.visualModeKeyBindings": [
{
"before": [ "<leader>", "e" ],
"commands": [ "hol4-mode.sendTactic" ]
},
{
"before": [ "<leader>", "s" ],
"commands": [ "hol4-mode.sendSelection" ]
},
],
"vim.normalModeKeyBindings": [
{
"before": [ "<leader>", "h" ],
"commands": [ "hol4-mode.startSession" ]
},
{
"before": [ "<leader>", "<leader>", "x" ],
"commands": [ "hol4-mode.stopSession" ]
},
{
"before": [ "<leader>", "s" ],
"commands": [ "hol4-mode.sendSelection" ]
},
{
"before": [ "<leader>", "<leader>", "s" ],
"commands": [ "hol4-mode.sendUntilCursor" ]
},
{
"before": [ "<leader>", "g" ],
"commands": [ "hol4-mode.sendGoal" ]
},
{
"before": [ "<leader>", "S" ],
"commands": [ "hol4-mode.sendSubgoal" ]
},
{
"before": [ "<leader>", "e" ],
"commands": [ "hol4-mode.sendTactic" ]
},
{
"before": [ "<leader>", "p" ],
"commands": [ "hol4-mode.proofmanShow" ]
},
{
"before": [ "<leader>", "b" ],
"commands": [ "hol4-mode.proofmanBack" ]
},
{
"before": [ "<leader>", "R" ],
"commands": [ "hol4-mode.proofmanRestart" ]
},
{
"before": [ "<leader>", "r" ],
"commands": [ "hol4-mode.proofmanRotate" ]
},
{
"before": [ "<leader>", "d" ],
"commands": [ "hol4-mode.proofmanDrop" ]
},
{
"before": [ "<leader>", "y" ],
"commands": [ "hol4-mode.toggleShowTypes" ]
},
{
"before": [ "<leader>", "a" ],
"commands": [ "hol4-mode.toggleShowAssums" ]
},
{
"before": [ "<leader>", "c" ],
"commands": [ "hol4-mode.interrupt" ]
}
]
}- Syntax highlighting is lacking. Logical terms are especially bad. The situation could be improved by implementing a HOL language server.
- There is some hacky code that attempts to strip ML comments from input that is being sent to HOL. Currently, this does not properly deal with nested comments, or comment tokens that exist within string literals.
- Comments are not stripped from tactic text.
loadcalls are not inserted when calls to qualified ML code is made.- Location pragmas are not inserted at calls to
{Co}Inductive,Datatype,Theorem, nor in term quotations. - Symbol search reaches only theories that have been built; a script
never compiled by
Holmakecontributes only the declarations of the buffers you have open. .sigfiles and library.smlfiles get no IDE features: the server binds to one theory script per process.