Skip to main content

Module config

Module config 

Source
Expand description

Root and layout resolution plus the optional on-disk configuration.

A tracker lives under <root>/<prefix>, one directory per project, each holding an issues.org. root comes from the caller, ISSUE_ROOT, VISSUE_ROOT, the working directory when that is itself a tracker, the seat’s own vissue/config.toml, and otherwise the working directory. prefix comes from the caller, VISSUE_PREFIX, <root>/vissue.toml, or the Software default.

The seat file is what lets the bare command answer from anywhere. Without it the only way to reach one tracker from outside its directory is an environment variable, which every shell and every launcher has to be told about separately, and a seat that misses one of them has a command that works in a terminal and not under an agent.

Structs§

ConsensusSection
Who listens to whom, and how hard the consensus iteration tries.
IssuesSection
Knobs that shape newly created issues.
Layout
Where the tracker lives: a root directory and the project prefix inside it.
VissueConfig
Effective configuration for one layout.

Constants§

DEFAULT_PREFIX
Directory under the root that holds one subdirectory per project.

Functions§

identity
Who is claiming work here.