[Org] Don’t use too large numbers in clock consistency checks

They could get too large and could be automatically converted to floats then,
resulting in strange errors.
This commit is contained in:
Daniel - 2017-10-30 20:04:45 +01:00
parent c67bfe2e17
commit bcac4afc03
Signed by: dbo
GPG Key ID: 4F63DB96D45AA9C6
1 changed files with 1 additions and 1 deletions

View File

@ -331,7 +331,7 @@ forces clocking in of the default task."
org-agenda-search-headline-for-time nil)
(setq org-agenda-clock-consistency-checks
'(:max-duration 999999999
'(:max-duration 9999999
:min-duration 0
:max-gap 0
:gap-ok-around nil