On Sun, 2017-05-21 at 10:47 -0500, Eduardo Bustamante wrote:

> FWIW, this seems to "fix" the issue.
...

Great! Any chance we could get this fix into the next release? :)

Reply via email to