diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-02 12:16:38 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-02 12:16:38 -0500 |
| commit | 8c32bbbf9fab115dc51afa17c081e0763cbee717 (patch) | |
| tree | 246b46b53c956cfea07bc9d1c2b81f9f8de53d65 /dotfiles/common/.zsh/modules/Test/B09hash.ztst | |
| parent | 3f370d6c19c83430547d1771b0e6fa669dc7d5c5 (diff) | |
| download | archsetup-8c32bbbf9fab115dc51afa17c081e0763cbee717.tar.gz archsetup-8c32bbbf9fab115dc51afa17c081e0763cbee717.zip | |
refactor: drop in-repo dotfiles/, move stow tooling to the dotfiles repo
Since the installer clones DOTFILES_REPO into ~/.dotfiles and stows from there, the in-repo dotfiles/ tree was dead weight. Nothing reads it at install time. I removed it (831 files) now that both machines are migrated.
The Makefile's stow / restow / reset / unstow / import targets and the dotfile-script unit suites moved to the dotfiles repo. They sit alongside the scripts they manage and run standalone (cd ~/.dotfiles && make ...). This Makefile keeps the VM-integration targets and the installer-helper suite (safe-rm-rf).
I updated CLAUDE.md and README.md so stow operations run from ~/.dotfiles, and the dotfile-management, theme, and unit-test sections point at the standalone repo. The README was already describing the old in-repo model from before the installer switched to cloning. This brings it in line.
Diffstat (limited to 'dotfiles/common/.zsh/modules/Test/B09hash.ztst')
| -rw-r--r-- | dotfiles/common/.zsh/modules/Test/B09hash.ztst | 79 |
1 files changed, 0 insertions, 79 deletions
diff --git a/dotfiles/common/.zsh/modules/Test/B09hash.ztst b/dotfiles/common/.zsh/modules/Test/B09hash.ztst deleted file mode 100644 index 7b5dfb4..0000000 --- a/dotfiles/common/.zsh/modules/Test/B09hash.ztst +++ /dev/null @@ -1,79 +0,0 @@ -# The hash builtin is most used for the command hash table, which is -# populated automatically. This is therefore highly system specific, -# so mostly we'll test with the directory hash table: the logic is -# virtually identical but with the different table, and furthermore -# the shell doesn't care whether the directory exists unless you refer -# to it in a context that needs one. - -%prep - populate_hash() { - hash -d one=/first/directory - hash -d two=/directory/the/second - hash -d three=/noch/ein/verzeichnis - hash -d four=/bored/with/this/now - } - -%test - - hash -d -0:Directory hash initially empty - - populate_hash - hash -d -0:Populating directory hash and output with sort ->four=/bored/with/this/now ->one=/first/directory ->three=/noch/ein/verzeichnis ->two=/directory/the/second - - hash -rd - hash -d -0:Empty hash - - populate_hash - hash -d -0:Refill hash ->four=/bored/with/this/now ->one=/first/directory ->three=/noch/ein/verzeichnis ->two=/directory/the/second - - hash -dL -0:hash -L option ->hash -d four=/bored/with/this/now ->hash -d one=/first/directory ->hash -d three=/noch/ein/verzeichnis ->hash -d two=/directory/the/second - - hash -dm 't*' -0:hash -m option ->three=/noch/ein/verzeichnis ->two=/directory/the/second - - hash -d five=/yet/more six=/here/we/go seven=/not/yet/eight - hash -d -0:Multiple assignments ->five=/yet/more ->four=/bored/with/this/now ->one=/first/directory ->seven=/not/yet/eight ->six=/here/we/go ->three=/noch/ein/verzeichnis ->two=/directory/the/second - - hash -d one two three -0:Multiple arguments with no assignment not in verbose mode - - hash -vd one two three -0:Multiple arguments with no assignment in verbose mode ->one=/first/directory ->two=/directory/the/second ->three=/noch/ein/verzeichnis - - hash -d t-t=/foo - i="~t-t" - print ~t-t/bar - print ${~i}/rab -0:Dashes are untokenized in directory hash names ->/foo/bar ->/foo/rab |
