excellent.
Thanks.
Carlos
On Tue, May 10, 2016 at 11:10 PM Nicolas Goaziou
wrote:
> Hello,
>
> Carlos Noguera writes:
>
> > FYI, I just discovered that the behaviour happens if "Org Clock Into
> > Drawer" option in "Org Clock group" is set to &qu
e the problem any more.
For the moment, I'll keep in " Into LOGBOOK drawer" as a workaround.
Hope this helps.
Carlos
On Tue, May 10, 2016 at 9:05 AM Carlos Noguera <
carlos.francisco.nogu...@gmail.com> wrote:
> Hi Nicolas,
>
>
> Here you have a trac
lock-string "
") (setq org-clock-effort ...) (setq org-clock-total-time ...) (setq
org-clock-start-time ...) (setq ts ...))) (move-marker org-clock-marker
(point) (buffer-base-buffer)) (move-marker org-clock-hd-marker
(save-excursion (org-back-to-heading t) (point)) (buffer-base-buffer))
When clocking in under a headline that already has clock entries, the
entries are not correclty bundled in a drawer, generating a: (I removed
the bytecode because gmail didn't like it)
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
byte-code("REMOVED" [beg end org-clock
