On Mon, Jan 14, 2013 at 9:31 PM, Michael T. Dean <mtdean at thirdcontact.com> wrote: > > Just update to current 0.26-fixes, which has a fix for the issue. Oh, good. That's on my to-do list. I looked through the commit messages for this, but must have missed it. Tom