I would like to see the behaviour of the "max_preludes" setting change:
- a value < 0 indicates an unlimited number of preludes
- a value of 0 disables preludes
- a value > 0 indicates the maximum number of preludes

This is already the case (with one small exception, -1 == unlimited)

It appears bugzilla is not mailing since the transition to sourceforge.
Testing, 1, 2, 3...

Ok. done. < 0 is now unlimited.

Note: WR now always shows a prelude window before a break window. Setting
"max_preludes" to 3. Will give 4 prelude windows. The first 3 show the text
"disappears in", the last one "break in". WR will force a break after this
prelude. (this is in case force_after_preludes is true, if this is false, only 3
preludes are shown, the last one has the text "silent in")

This behaviour is very confusing. 

From a user point of view, there is not much difference between the last 
prelude and the earlier ones (I even call them the same).

So I think that the "max preludes" field should count all preludes (including 
the last one).

I thought this was what we agreed on over dinner? It's not currently 
implemented.

I'm even more confused.

The prelude window says "Break in x:xx", with x:xx some number that is counting 
down.

So I'm idle, waiting for the counter to reach zero and my break to begin. 
However, when wr detects I'm idle, it removes the prelude and shows the break 
window, apparently ahead of time.

I know this is exactly how we specced it, but still I find this confusing.

Fixed "max_preludes" behaviour. Wrt to the "Break in x:xx": reopen bug with
alternative.