Dotdrop version (and git commit if run from source): v0.xxx
Using dotdrop: AUR 1.16.2-1
Describe the bug
When deleting a folder then updating the dotfiles, dotdrop will prompt whether you want to recursively remove every single child and descendant of the folder, often removing the whole folders midway then continuing to ask
Steps to Reproduce
Steps to reproduce the behavior:
- Delete a folder containing several children and/or descendants (nested children) being tracked by dotdrop (usually within another folder listed within config.yaml)
- Update the dotdrop profile
Expected behavior
Dotdrop should detect when a folder is deleted rather than naively check all of the descendants (which won't exist) and prompt
Additional information
Command: dotdrop update -p profile
Example output (paraphrased):
Recursively remove "/home/whatever/dotfiles/config/app/config.yaml" ? Y
Recursively remove "/home/whatever/dotfiles/config/app" ? Y
Recursively remove "/home/whatever/dotfiles/config/app/style.css" ? Y
Dotdrop version (and git commit if run from source): v0.xxx
Using dotdrop: AUR 1.16.2-1
Describe the bug
When deleting a folder then updating the dotfiles, dotdrop will prompt whether you want to recursively remove every single child and descendant of the folder, often removing the whole folders midway then continuing to ask
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
Dotdrop should detect when a folder is deleted rather than naively check all of the descendants (which won't exist) and prompt
Additional information
Command: dotdrop update -p profile
Example output (paraphrased):
Recursively remove "/home/whatever/dotfiles/config/app/config.yaml" ? Y
Recursively remove "/home/whatever/dotfiles/config/app" ? Y
Recursively remove "/home/whatever/dotfiles/config/app/style.css" ? Y