Tools for writing Tree-sitter grammars in Pulsar, including a grammar for Tree-sitter query files.
IMPORTANT: Currently works on Pulsar v1.106 and newer. Versions 1.106 through 1.112.1 need the core.useExperimentalModernTreeSitter setting enabled; versions 1.113 and newer enable modern Tree-sitter grammars by default.
The Tree-sitter inspector pane is an enhanced version of the Tree-sitter playground.
When inside of a buffer using a modern Tree-sitter grammar, you can open the editor any of the following ways:
- Invoking the Tree Sitter Tools: Open Inspector For Editor command.
- Right-clicking on an editor and selecting the Open Tree-sitter Inspector For Editor.
- Invoking the hotkey: Ctrl+Alt+Shift+I.
- Selecting Packages → Tree-Sitter Tools → Open Inspector For Active Editor from the application menu.
A pane will open on the right side showing a representation of the editor’s Tree-sitter tree.
Here’s what you can do:
- Clicking any node in the tree will select the corresponding editor range.
- Clicking any node will also log the node itself to the developer tools console for inspection.
- Moving the cursor will change what is focused in the inspector.
- You may toggle whether anonymous nodes are shown or hidden in the tree.
- You may choose a different “language layer” via the drop-down menu if more than one layer is present. The first item in the list will always be the root language layer. If the layer you’re inspecting is destroyed as a result of buffer changes, the view will reset to the root layer.
- When you are inspecting a language layer other than the root, you may check the “Show injected ranges” checkbox to see the current content ranges of that layer’s injection. Editing the document while this option is checked is a useful visualization of how injection layers are re-processed in response to changes.
The query field is shown below the node inspector and accepts any valid Tree-sitter query syntax.
When a query runs, each capture name in the query will be annotated with a colored decoration, and any matches for that capture in the editor will have the same decoration.
The decorations will persist through editor changes, and will update when the editor updates. When the active layer is changed, the query editor will clear.
Keep in mind that some predicates are not implemented in the web-tree-sitter bindings, even if they’re present in the documentation and in sample query files in Tree-sitter parser repositories.
The built-in predicates #match? and #eq? are supported, as are certain custom predicates supported by Pulsar via #is?, #is-not? and #set!:
- scope tests (e.g.,
(#is? test.first)) will be applied, and any captures that fail their tests will not be decorated. - scope adjustments (e.g.,
(#set! adjust.startAndEndAroundFirstMatchOf "^#")) will be applied, and the adjusted range will be decorated rather than the original capture range.
A grammar for Tree-sitter query files is included.
- Ability to view or copy a node’s own
toString(its description of itself in query syntax) - Modes for assisting in writing and debugging queries for indents and folds