Good catch! Though it has been known since v0.1.4, nonetheless it doesn't come up much, so this report is helpful in determining the priority of a fix. As it stands it's pretty low since it's relatively easy to avoid. ;-)
-Cheers
