diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-23 20:20:17 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-23 20:20:17 -0500 |
| commit | 5ae97f905186d52abb6fd509193c802c5d4e4e2b (patch) | |
| tree | d856a2d080e7daf23b1078b6f8ee71f174395296 /tests/test-custom-ordering-arrayify.el | |
| parent | e25751c1a8673855bc8235288e7544078a1b14dc (diff) | |
| download | dotemacs-5ae97f905186d52abb6fd509193c802c5d4e4e2b.tar.gz dotemacs-5ae97f905186d52abb6fd509193c802c5d4e4e2b.zip | |
fix(dwim-shell): make destructive file-op commands match their names
Two commands did less, or more, than their names implied.
remove-empty-directories ran find . -type d -empty -delete from whatever the current directory happened to be, so its scope was implicit and easy to misjudge. It now prompts for a root, names that root in the confirmation, and runs find against the shell-quoted root via cj/dwim-shell--empty-dirs-command.
secure-delete ran shred without -u, so it overwrote a file's contents but left the file in place, not the deletion the name and the "permanently destroy" prompt promise. Added -u so it unlinks after overwriting.
Diffstat (limited to 'tests/test-custom-ordering-arrayify.el')
0 files changed, 0 insertions, 0 deletions
