On Friday, 20 January 2017 at 07:54:10 UTC, Jacob Carlborg wrote: > It does. It's been fixed, for exactly this reason. This has already been fixed? Is this fix in a stable release yet? I might not be on the latest version...