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
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 "When at least N clock
> entries: 3" and I go from two entries to 3.
> If I change it to "Into LOGBOOK
Hello Nicolas,
FYI, I just discovered that the behaviour happens if "Org Clock Into
Drawer" option in "Org Clock group" is set to "When at least N clock
entries: 3" and I go from two entries to 3.
If I change it to "Into LOGBOOK drawer" I don't have the problem any more.
For the moment, I'll
Hi Nicolas,
Here you have a trace with an uncompiled Org. Let me know if you need
something else.
Carlos.
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
insert(":" nil ":\n")
(save-excursion (insert ":" drawer ":\n"))
(let ((end (point-marker))) (goto-char beg)
Hello,
Carlos Noguera writes:
> 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:
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