This bug has been resolved in the git repository, and the fix will (along
with a few other fixes) be rolled into a 0.7.3 release fairly soon.

Reply via email to