I cannot reproduce this bug with version 0.8.6-2, either. I suppose that 0.8.6 has fixed this bug, as already observed by Patrick Schoenfeld. This bug should probably be closed. -Ralf.