please close this bug.
It was addressed, and the current version 2.1.5 behaves as desired.

   Bram Stolk

Reply via email to