Noodlesoft Forums

Hi, I noticed that when I try to move or copy a file (test.txt) from
Disc 1/this/specific/path to Disc 2/that/other/path
Hazel does not do what, say, the "mv"-command would do, but instead, it seems to do this:

1. Hazel creates a new folder: Disc 1/(A Document saved by hazelworker).
2. Hazel copies/moves test.txt from Disc 1/this/specific/path to Disc 1/(A Document saved by hazelworker).
3. Hazel copies/moves test.txt from Disc 1/(A Document saved by hazelworker) to Disc 2/that/other/path.

Now I would not mind at all, but in this case, I am moving files that need to go into an encrypted container (mounted into the file system). The problem with how Hazel seems to work is step 2, because there the file touches unencrypted space, hence the encryption is broken at this point and this action becomes useless.

So my question is: Except removing Hazel from the process, is there a setting/an action I could make use of in Hazel that works like the mv-command does, i.e. no extra folders being generated, but moving the file directly from Disc 1 to Disc 2?

Thank you,
Michael

Hazel will try and copy a file to temp space on the destination drive. That way you won't see an incomplete file in the destination folder. If there is no temp space to use, it will just use the destination folder. Not sure why it is doing it at the source. Have you checked the contents of that file to make sure it's the actual file? Note that "A document saved by" file is something generated by the OS. I do not create that explicitly but seems to be a side effect of the API calls I am using.