| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A feed watcher may fail to reschedule, for example if it was stopped
before completion. Fail graciously warning the user.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
help message improved.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
nonconformat headers.
|
|
|
|
|
|
The timer blocks are closures, so they inherit the variables in the scope they were created. Passing those same variables to the block as data is useless.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Since the timer fix in [1035], rescheduling ticks the timer, which could cause the timed saving to trigger while a feed mutex was being held. Fix by moving the feed watcher rescheduling out of the mutex synchronization.
Also move other calculations out to hold the mutex for as little as necessary.
|
|
This ensures that locale files are found regardless of rubygems being loaded or not
|
|
returning a language string
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
