Timing for "watch for (silence|activity)" plugin

Asked by Sparhawk on 2014-08-31

I was wondering how long it takes for the "watch for (silence|activity)" plugin to trigger, and if it were possible to modify this. I have a build that takes about 20 minutes to run, but output pauses occasionally for half a minute. I'd like to lengthen the "watch for silence" trigger, to reduce false positives.

Question information

Language:
English Edit question
Status:
Solved
For:
Terminator Edit question
Assignee:
No assignee Edit question
Solved by:
Stephen Boddy
Solved:
2014-09-20
Last query:
2014-09-20
Last reply:
2014-09-19
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Sparhawk (sparhawkthesecond) said : #2

Bump.

It looks like it is hard-coded in terminatorlib/plugins/activitywatch.py at 10 seconds for both activity and inactivity. See lines 80 and 149 of the trunk.

You could just change those values locally, or someone could improve the plugin to present a config option.

It actually looks like someone has made the value configurable here:
https://code.launchpad.net/~joseph-crosland/terminator/terminator/+merge/224909

(I haven't looked at this yet or merged it, so use at your own risk!)

Sparhawk (sparhawkthesecond) said : #5

Thanks for the answer, Stephen. I'll wait for the changes in the merge, as I don't really want to make changes to system files that will potentially get overwritten in an update. Thanks again.

Sparhawk (sparhawkthesecond) said : #6

Thanks Stephen Boddy, that solved my question.