Jan M. Faber

Just drop this in config/initializers/mail_patch.rb to make mail produce RFC compliant emails again, it simply patches back the function from before the bug was introduced. ``` module Mail module Encodings...

Interesting suggestion, and I agree that might be better than introducing a new configuration option. It doesn't currently work however. It looks like `ensure_stage` verifies the task at hand before...

Yes, it looks like there already is a `@top_level_tasks` that contains what you need, so the check would need to see if one of the prerequisites is in there.

It turns out that this can be done by adding a single line to the `ensure_stages` method. I love how succinct ruby makes this monkey patch: ```ruby module Capistrano module...

Sure, I guess a switch to puma would be OK. Currently nanoc view has `DEFAULT_HANDLER_NAME = :thin` in it, so we would probably want to change that, to prevent having...

I switched to puma but I noticed there is about a 25% chance that it leaves behind a ruby process when quiting nanoc live with ctrl-c. Webbrick appears to quit...

For me simply adding the puma gem to the bundle, doing `bundle exec nanoc live` and then ctrl-C right after still consistently hangs and leaves a ruby process behind. No...

While we're on the subject the output also lists "mongrel" as an example, a web server that no longer exists. And the host and port both show the default value...

I took a brief look at the code but I don't understand yet why a valid date will _not_ raise and exception. So it's doing validation somewhere anyway. A workaround...

I mean this: ``` Psych.safe_load('2013-01-01'.to_yaml) # => "2013-01-01" Psych.safe_load('2013-02-31'.to_yaml) # Psych::DisallowedClass ``` So some date parsing is apparently already happening somewhere, I just haven't been able to find it in...