-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore list #1
Comments
There's a need. But in my mind, backdown is something you don't really prepare, it's something you launch every 10 years or so, when your disks are too messy. And you maybe don't remember how it works. So I'd rather have an option in questions, like "[i] change ignore list" opening a new set of questions about what to add to ignore list (which I didn't think about yet enough). It would be saved for later use. |
That sounds perfectly workable. If the app's ignore list was externally editable that would target both use cases. My particular first run picked up on the plethora of node_modules folders in my work dir and found a LOT of dupes therein :) |
I tried to warn against that at the end of the README: backdown isn't tailored to handle dev directories. An option to follow gitignore rules could help but I'm not sure there's ever valid reasons to try deduplicate dev directories (except the few "myproject-save" dirs but you can remove them without a tool). |
Making the file editable and read before every question is totally doable, though. |
Oh yeah, understood... The first thing anyone does with something new is try to use it as it wasn't intended though :) |
It would be handy to have some regex-based mechanism for ignoring certain files/directories, especially for repeated runs. Maybe also an option to add certain found dupes to a global ignore file.
The text was updated successfully, but these errors were encountered: