Guard 2.0 compatibility

[imathis]

Guard now expects to find the Guardfile template in lib/jekyllplus/templates/Guardfile instead of lib/jekyll-plus/templates/Guardfile. Also there are other issues related to notifications.

[taiansu]

I dug a little bit and found while executing this line , The notifiers array should be

    [{:name=>:terminal_title, :options=>{:silent=>true}}]

become

    [{":name"=>":terminal_title", ":options"=>{":silent"=>true}}]

And the culprit could be that guard use YAML.dump and YAML.load to save and load the notifiers.
After hacking out this part, this plugin works quite normally all along. (Conflict with guard-coffeescript).

[imathis]

@taiansu thank you for looking into this. I hadn't gotten as far as you have. Reading your comment, it sounds like you're saying that this isn't a problem with GJP but Guard itself. Is that correct, or is there some way I can fix my own project?

[janko]

Just to let you know, safe_yaml, on which Jekyll depends, is causing this problem. It modifies YAML.load to be safe, so it doesn't turn ":keys:" into :keys anymore, but rather into ":keys" (like seen above).

[imathis]

@janko-m Thanks for the update. Do you have a suggestion for how I can fix this?

[janko]

I'm actually not using Guard, my brother (who is a designer, but not a Rubyist) had an issue with this, so I looked into it, and figured I could as well let you know :)

There is a way to require safe_yaml without monkey patching existing YAML, but that's not what's Jekyll's doing :P. So I don't have any ideas on top of my head.

[imathis]

Thanks for pitching in. So it sounds like my best bet would be to try to convert these hashes to :keys before handing them off to guard.