Documentation at https://melpa.org/#/treefactor

K-D tree spatial indexing structure.

Rust bindings to the Tree-sitter parsing library

Rust bindings to the Tree-sitter parsing library

This package provides a YAML grammar for the Tree-sitter library.

This package provides a YAML grammar for the Tree-sitter library.

A sorted dictionary data structure based on red-black trees.

This package provides Rust bindings to the Tree-sitter parsing library.

This package provides a Bash grammar for the Tree-sitter library.

This package provides a Heex grammar for the Tree-sitter library.

This package provides a JSON grammar for the Tree-sitter library.

This package provides a HTML grammar for the Tree-sitter library.

This package provides a Java grammar for the Tree-sitter library.

This package provides a Rust grammar for the Tree-sitter library.

This package provides a VHDL grammar for the Tree-sitter library.

This package provides a Sway grammar for the Tree-sitter library.

This package provides a Ruby grammar for the Tree-sitter library.

This package provides a YAML grammar for the Tree-sitter library.

Spatial-trees is a set of dynamic index data structures for spatially-extended data.

This module in a fully object-oriented implementation of a simple n-ary tree.

pst-tree defines a macro \pstree that offers a structured way of joining nodes created using pst-node in order to draw trees.

This package provides a tree-structured thread pool for splitting jobs hierarchically on worker threads. The tree structure means that there is no contention between workers when delivering jobs.

Syntax Tree is a suite of tools built on top of the internal CRuby parser. It provides the ability to generate a syntax tree from source, as well as the tools necessary to inspect and manipulate that syntax tree. It can be used to build formatters, linters, language servers, and more.

This data structure can be used to store the history of visited paths or URLs with a file or web browser, in a way that no “forward” element is ever forgotten.

The history tree is “global” in the sense that multiple owners (e.g. tabs) can have overlapping histories. On top of that, an owner can spawn another one, starting from one of its nodes (typically when you open a URL in a new tab).