Bastien <b...@altern.org> writes: > Carsten Dominik <carsten.domi...@gmail.com> writes: > >> Also, this new property, when set, does not allow :clock-resume, >> I have not checked if something bad would happen should a user >> give both by accident. > > Ah yes, thanks for bringing this up: :clock-keep has precedence > over :clock-resume -- when both are non-nil, :clock-resume will > be discarded. I mentioned this in the manual.
For my 't' capture template with :clock-in and :clock-resume (and no :clock-keep) when I start capture mode for the task when the clock is not running it stays running in that task (as reported earlier) - Isn't that a bug? Thanks, -- Bernt
