Bluepill swallows unknown process configuraton attributes silently #40
Description
I ported some configuration over from eye. As there was no error when launching bluepill, I assumed all options are working correctly.
I now discovered I was using a non-existing option inside a process block. As it turns out, bluepill accepts any option given in a process block. But only known options will be used. As a consequence, it is impossible to determine which options are actually being used. It was rather surprising and hard to find out the cause of these problems.
In my opinion, this is actually bad behaviour for a Ruby DSL. A configuration file which contains invalid options should lead to an error instead. I believe this would be rather easy to implement. Please consider adjusting the code accordingly.
That said, thanks for the the work on a very useful project!