The comment mentions one behaviour but the test was performing another.
It was also failing for a different reason, which is filters with no
matches always exit with non-zero. If the correct behaviour is indeed
expiring all recurring tasks, the test must use runError instead.
Also added a TODO for easier finding.
I'm a little unsure about the correct behaviour here.
I would expect both features to depend on rc.recurrence.confirmation and
not rc.confirmation. Yet when rc.confirmation=on no prompt is shown
about recurring parents.
- Adding an 'until' date to a recurring task is propagated to the task instances
and they expire at the same time. It was assumed otherwise, but the working
behavior is better.
