You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The link step decides which files in $HOME point into this repo, and its 28 link.bash files are tested only by running them as bash against a fake HOME. Each one sources tools/bash/utils.bash for symlink(), features/update/symlinks.bash runs them all, and scripts/checks/link-scripts.bash checks that each writes nothing when DOTFILES_CHECK=true.
Ideal state
Every tool's link step is Python, tested by tests that import it
symlinks, dcheck and u create, report and sweep the same links as before
docs/invariants/tools.md: with DOTFILES_CHECK=true a link step still writes nothing, and config is still symlinked rather than copied
Open
What command starts the repo's Python? (new CLI contract) Open in what-command-starts-the-repos-python.md. It is settled before this issue starts, and this is the first category to use it.
Starting points
tools/bash/utils.bash: symlink(), which every link step calls
features/update/symlinks.bash: sweeps broken links and runs every link step
features/update/tests/test_symlinks.py: how the link step is tested today
Depends on
The sub-issue that sets up the repo-level Python project: the ported code needs the project to live in
Activity