For the record, this is fixed in the latest Plan, version 1.12 (it was not 
available when I first reported this bug).

Reply via email to