diff options
author | Christian Wieninger <cwieninger@gmx.de> | 2011-05-28 15:02:17 +0200 |
---|---|---|
committer | Christian Wieninger <cwieninger@gmx.de> | 2011-05-28 15:02:17 +0200 |
commit | d71b080637c5eba84854f2338b53fdda8fc6ed34 (patch) | |
tree | 3efefac4793302cc85b89c5eb08c72814a0960a9 /doc-src | |
parent | 280c12c3c7042e176c6acc3bd7718f66cd9eb39d (diff) | |
download | vdr-plugin-epgsearch-d71b080637c5eba84854f2338b53fdda8fc6ed34.tar.gz vdr-plugin-epgsearch-d71b080637c5eba84854f2338b53fdda8fc6ed34.tar.bz2 |
new setup variable epgsearch.ConflCheckCmd
Diffstat (limited to 'doc-src')
-rw-r--r-- | doc-src/en/epgsearch.4.txt | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc-src/en/epgsearch.4.txt b/doc-src/en/epgsearch.4.txt index dd0db6b..6257499 100644 --- a/doc-src/en/epgsearch.4.txt +++ b/doc-src/en/epgsearch.4.txt @@ -647,6 +647,19 @@ timer (like modifying start/stop or deleting a timer) in the conflict details menu also cause an immediate return to the overview menu and produce an update. +Note: +There's a 'hidden' setup option epgsearch.ConflCheckCmd, that allows executing a +command for each timer causing a conflict. You have to set this directly in VDRs +setup.conf like this: + +epgsearch.ConflCheckCmd = system(your_script_handling_the_conflict.sh, any_arguments like %timer.file%) + +(Please have a look at 'Calling a system command' below for the possible arguments) +One could use this for example to forward a timer to another VDR machine in case of a conflict. +This command is evaluated for each timer causing a conflict whenever an automatic +conflict check is running. When calling the conflict check via OSD the command is not +evaluated. + =head1 12. User defined variables You can create your own variables to be used in any place that supports |