I had another look at my above published Terminal command and made it more bullet-proof.
- it touches only real folders, not files;
- it drills recursively down into subfolders, subsubfolders etc;
- applications are, for Terminal, also folders, but they are skipped (new);
- Library folder is skipped (new);
- folders without the FinderInfo generate an error that we don't want to see;
- but real errors (there shouldn't be) are displayed (new).
find $PWD -type d -not \( -path "*.app" -prune \) -not \( -path "$HOME/Library" -prune \) -exec xattr -d com.apple.FinderInfo {} \; 2>&1 | grep -v -e 'No such xattr'
(copy the complete italic line(s) above, paste in Terminal and hit return)
Don't use the command with your root-folder, your startup disk, as starting point. System and Library and a lot of invisible Unix folders are there that you don't want to process.
OK are:
- your home folder, where Terminal is when you launch it
- one up, the Users folder: cd /Users
- all other folders, except System and Library: cd drag&drop_a_folder_into_Terminal
- external disks with just data and applications (but not a complete CCC backup, with System etc)
In Terminal file- or folder-names with funny characters ($/`| etc) can cause problems, but find is quite safe in this regard. And be patient, the execution can take quite some time.
(my problem with other shorter solutions here is that they also process files and applications)