Tree-like interface to Emacs undo system, providing graphical tree presentation of all previous states of buffer that allows easily move between them.
TreeLayout creates tree layouts for arbitrary trees. It is not restricted to a specific output or format, but can be used for any kind of two dimensional diagram. Examples are Swing based components, SVG files, etc. This is possible because TreeLayout separates the layout of a tree from the actual rendering.
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).
Tree-sitter is a parser generator tool and an incremental parsing library. It can build a concrete syntax tree for a source file and efficiently update the syntax tree as the source file is edited.
Tree-sitter aims to be:
General enough to parse any programming language.
Fast enough to parse on every keystroke in a text editor.
Robust enough to provide useful results even in the presence of syntax errors.
Dependency-free so that the runtime library (which is written in pure C) can be embedded in any application.
This package includes the tree-sitter
command-line tool.
Tree-sitter is a parser generator tool and an incremental parsing library. It can build a concrete syntax tree for a source file and efficiently update the syntax tree as the source file is edited.
Tree-sitter aims to be:
General enough to parse any programming language.
Fast enough to parse on every keystroke in a text editor.
Robust enough to provide useful results even in the presence of syntax errors.
Dependency-free so that the runtime library (which is written in pure C) can be embedded in any application.
This package includes the tree-sitter
command-line tool.
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.
This package provides a Heex grammar for the Tree-sitter library.
This package provides a VHDL grammar for the Tree-sitter library.
This package provides a Ruby grammar for the Tree-sitter library.
This package provides a Bash grammar for the Tree-sitter library.
This package provides a JSON grammar for the Tree-sitter library.
This package provides a Rust 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.
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).
This package is used for bundling related git-worktrees from multiple repositories together. This helps switch quickly between repositories and ensure you're on the correct branch. When you're done with your changes, you can use the repositories in the workspace and know which ones were modified to simplify the process of getting the changes merged in together. Additionally, git metadata is shared between all projects. You can stash, pop, and pull changes in from the same repository in other workspaces thanks to the power of git-worktrees.