[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:
parent
c67bfe2e17
commit
bcac4afc03
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue