- Code: Select all
2009-07-28 09:41:41.630 hazelfolderwatch[35617] DSCN0835.JPG: Rule Images matched.
2009-07-28 09:41:58.060 (null)[0] DSCN0835.JPG: Rule Images matched.
2009-07-28 09:42:23.112 (null)[0] DSCN0835.JPG: Rule Images matched.
I have noticed, sometimes, if I move the (null)-identified file to an unwatched folder, Hazel will happily work on the next files in line, until it finds another (null) file. At that point it again completely stops sorting files.
Right now I have 48 files in my downloads folder (mostly JPGs with a few FLV, MP3 and DMG files), and it looks like all of them are causing the (null) message. Since this started happening, I've turned off all my rules except for one... a simple one to sort all JPGs in my downloads folder to subfolders based on the web site I downloaded them from.
When I turn debugging on it looks like this:
- Code: Select all
2009-07-28 09:21:45.540 (null)[0] DEBUG: Program is licensed.
2009-07-28 09:21:45.544 hazelfolderwatch[29691] DEBUG: Could not scan past browser.download.dir preference
2009-07-28 09:21:45.553 hazelfolderwatch[29691] DEBUG: Initialized
2009-07-28 09:21:45.553 hazelfolderwatch[29691] DEBUG: Pausing to wait for things to settle down.
2009-07-28 09:21:47.554 hazelfolderwatch[29691] DEBUG: Processing directories: (
"/Users/mrpeanut/Downloads"
)
2009-07-28 09:21:47.554 hazelfolderwatch[29691] DEBUG: About to process directory /Users/mrpeanut/Downloads
2009-07-28 09:21:47.573 hazelfolderwatch[29691] DSCN0834.JPG: Rule Images matched.
2009-07-28 09:21:47.573 hazelfolderwatch[29691] DEBUG: New rule signature. Executing actions.
Old signature: (null)
New Signature:{typeObject isType: "public.image" OR extension LIKE[cd] "jpg"}:{(createfolder:(
Images,
{pathSeparator},
"Images (",
{sourceDomain},
")"
),{
})}
Any idea what's going on?