I've noticed that the move command in Hazel just copies the file and then deletes the original.
Is there any reason or fix for this? It's pretty slow when interacting with large files.
Moderators: Mr_Noodle, Moderators
Mr_Noodle wrote:Do you have any sort of logs showing that this is happening?
Mr_Noodle wrote:What happens if you do the same move manually with Finder?
Mr_Noodle wrote:Does the filename contain any colons or slashes? If so, do you notice different behavior on files that don't contain those characters?
Overall, it seems weird. Ultimately, Hazel is using Apple's routines to perform the move so the decision to do a copy/delete is happening within Apple's code. Hopefully, if we can isolate it, I can file a bug with them about it or figure out some sort of workaround.
Mr_Noodle wrote:Can you described what happened? You can't just leave me hanging here!