@gattermann this bug is there since 2.0; it’s so obvious that there must be a reason for not fixing it /cc @atebits