I fixed this in version 0.9.1 (just released) thanks for the bug (seriously)