Closed 2V3EvG4LMJFdRe closed 2 years ago
From the docs
clutter
When beets imports all the files in a directory, it tries to remove the directory if it’s empty. A directory is considered empty if it > only contains files whose names match the glob patterns in clutter, which should be a list of strings. The default list consists of “Thumbs.DB” and “.DS_Store”.
The importer only removes recursively searched subdirectories—the top-level directory you specify on the command line is never deleted.
The last sentence might explain your observations — whether that is a sensible action for the clutter
option probably depends on how you organize your files before importing them.
Hmm, I see. I think most people use beet pointing to the folder of a single album to scan, without any subfolders on it (something like "scans" or "booklet" is all I've ever seen in other people's collection). IMO the most logical use for clutter
would be to remove an album's folder after importing it (I keep having to go back to my downloads
folder and see which folders are leftovers after a successful beet import).
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Problem
Running this command in verbose (
-vv
) mode:Led to:
There's no mention of anything about clutter and the folder is not removed. This happens with any folder. I'm testing it with a test.cue file, which is the sole file remaining on it after beet runs.
Setup
It's been like this for a while, not sure it ever worked.
My configuration (output of
beet config
) is: