silentbob

@juanpicado Thanks for your answer. I totally understand your concern about making this an option instead of the default behaviour and I can update the PR accordingly. Regarding `fs.watch`: I...

I did open the developer tools (Ctrl+Shift+I) and ran a refresh targets. Did not show any additional message at all. I set a breakpoint in the refreshtargets function and the...

I replaced require with readfile and parse for JSON file. This works for me, and refreshes the targets. ~~I'm pretty sure, this issue applies for .js files too, but I...

@jmariner Thanks for your comment. I already figured this out quite a while ago (see the comments in #542 for details) long story short: atom won't change the current behavior....

@mooosh-milllie That's exactly what the issue is about: `2-59/10 * * * *` should be equivalent to `2,12,22,32,42,52 * * * *` but with `node-cron` it's (wrongly) expanded to `10,20,30,40,50...

@mooosh-milllie You don't get the point. This issue has nothing to do with when you start you task. The problem is, `node-cron` expands a pattern like `2-59/10 * * *...

Actually, this is also wrong for days. A pattern like `0 0 */2 * *` will run on the 2nd, 4th, 6th ... day of every month instead of 1st,...

But actually, this wrong behavious seems to be intentional (or just easier to implement). At least it's documented this way ... > e.g: 1-10/2 that is the same as 2,4,6,8,10...

@mooosh-milllie I don't know which version of `node-cron` you are using or where you got it from. But the one in this repository explicitely has written in the docs that...

fixes #192