Code review comment for lp:~marco-gallotta/ibid/uva

> I'm not sure how I feel about setting the current contest via config. Config
> is for, well, configuration.
>
> I'd prefer "monitor uva <id>" -- and if there's only one running contest (this
> usually seems to be the case on UVa) then one shouldn't need to specify.

I originally had it like you suggest, but there were a few issues with that -- maybe we can get past them though. The "uva countdown" feature works before the contest starts -- perhaps it can be made to countdown to the next contest and take an optional <id> arg. The "uva scoreboard" feature only could do the same -- except, it uses the current/previous contest if an <id> is not provided.

Usage would then become

14:37 < mibid> marcog: You can use uva in the following ways:
14:37 < mibid> uva countdown <contest_id>
14:37 < mibid> uva scoreboard <contest_id>
14:37 < mibid> monitor uva <contest_id>
14:37 < mibid> stop monitoring uva

Sound good?