Closed this issue 6 years ago · 0 comments
This issue was initially reported in #15 and fixed as of 136be46. It seems the bug must have returned as a regression at some point.