Geektool 3

When GeekTool fails to run a shell command, it logs the error to system.log (for example "Badly placed ()'s.". That's great, but it would be even better if it indicated which geeklet returned that error (by name if the geeklet's name was defined or by id if it wasn't).

I also find a fair number of "Task already running" in the logs. Is that caused by a geeklet trying to run again while the previous run hasn't completed yet? If so, it would also be cool to know which geeklet triggered that error. BTW, if I'm right about the cause of this error, couldn't you simply set the timeout internally to always be a bit lower than the refresh time (I mean even if the user didn't define a timeout)?