It would be great if you could comment on the original bug reports and
link to a new one. This should get fixed if is indeed broken again in
2016.3 and it would be a pity if it stays that way, just because a post
on a mailing list didn't receive the attention it deserves.
Thank you!
> Is this an accidental regression? Or should I not assume that fixes in
> previous releases would be included in the later release?
I haven't had time to check this, but it should™ be fixed in 2016.3 if
it had been fixed in 2015.8.10.
--
Wolodja Wentland <
bab...@gmail.com>
4096R/CAF14EFC
081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC