Moving any file to the trash takes seconds to minutes (compared to instantly from the commandline).
Moving or renaming files can sometimes be very slow.
Emptying the trash fails due to clear false positives about files still being in use.
And often they fail instead of just being slow, erroring with messages like "can't be moved right now".
These issues do not occur when using the commandline or e.g. moving/editing files using VS Code's UI, with the exception of the rm -rf ./node_modules issue.
I think some of this is due to the aggressive creation of .DS_Store files, but it can't explain everything.
I just renamed a file successfully in Finder. The rename was instantly successful, but it took nearly a minute for VS Code to see the renamed file! 😳
rm -rf ./node_modules
fails regularly.And often they fail instead of just being slow, erroring with messages like "can't be moved right now".
These issues do not occur when using the commandline or e.g. moving/editing files using VS Code's UI, with the exception of the
rm -rf ./node_modules
issue.I think some of this is due to the aggressive creation of
.DS_Store
files, but it can't explain everything.Similar issues on the internet: 1