Hello,
Samuel Wales writes:
> clocking in produces this bt:
>
> Debugger entered--Lisp error: (wrong-number-of-arguments decode-time 2)
I see. The you are missing b561c8b7efa5e88763c67d9327507e01af601352.
You need to update Org.
Regards,
--
Nicolas Goaziou
On 8/8/17, Nicolas Goaziou wrote:
> Then I cannot reproduce it. Either from maint or master branch.
i am using vanilla org 9 maint which is recent as of your fixes, emacs
-Q from debian which is 24.4.1, my test case, and this command line:
clocking in produces this bt:
Hello,
Samuel Wales writes:
> On 8/7/17, Nicolas Goaziou wrote:
>> I'm not sure about the steps required to reproduce your issue. What do
>> you do on the same mwe? Clock in
>>
>> "* clock in here, then sort below, then try to clock out here"
>>
On 8/7/17, Nicolas Goaziou wrote:
> I'm not sure about the steps required to reproduce your issue. What do
> you do on the same mwe? Clock in
>
> "* clock in here, then sort below, then try to clock out here"
>
> then sort at
>
> "*** sort here by alpha"
>
> then clock
Hello,
Samuel Wales writes:
> i seem to get another bug, no active clock, on the same mwe:
>
> :LOGBOOK:
> CLOCK:
> :END:
>
> if i use -Q with these settings:
>
> (setq org-log-into-drawer t)
> (setq org-clock-into-drawer t)
> (setq org-clock-mode-line-total 'today)
>
On 8/7/17, Nicolas Goaziou wrote:
> Fixed. Thank you.
thank you!
i seem to get another bug, no active clock, on the same mwe:
:LOGBOOK:
CLOCK:
:END:
if i use -Q with these settings:
(setq org-log-into-drawer t)
(setq org-clock-into-drawer t)
(setq
Hello,
Samuel Wales writes:
> this mce produces "clock start time is gone" bug in emacs -Q. emacs
> 24, org maint.
>
> ===
> * b
> * clock in here, then sort below, then try to clock out here
> *** SOMEWHAT b
> *** c
> *** c
> *** c
> *** c
> *** sort here by alpha
>
this mce produces "clock start time is gone" bug in emacs -Q. emacs
24, org maint.
===
* b
* clock in here, then sort below, then try to clock out here
*** SOMEWHAT b
*** c
*** c
*** c
*** c
*** sort here by alpha
* asdfasd
* asdfasd
* asdfasd
* asdfasd
* asdfasd
*** c
*** c
perhaps it could put a temporary uuid in the task so that it knows
where to go? silly idea, but i don't think i will be able to create
an mce.
On 6/14/17, Nicolas Goaziou wrote:
>> just curious but why does it unless actually gone? can't it just
>> check logbook drawer
Hello,
Samuel Wales writes:
> On 6/6/17, Nicolas Goaziou wrote:
>> This is odd, as this shouldn't be usual.
>
> just curious but why does it unless actually gone? can't it just
> check logbook drawer top line for a clock line?
The active/last
On 6/6/17, Nicolas Goaziou wrote:
> This is odd, as this shouldn't be usual.
just curious but why does it unless actually gone? can't it just
check logbook drawer top line for a clock line?
> It is possible if you have really large clock drawers, i.e., hundreds of
>
Hello,
Samuel Wales writes:
> recent maint.
>
> just wondering what i could be doing wrong.
>
> it is /usually/ the case that i get clock start tmie is gone when i
> try to clock out.
This is odd, as this shouldn't be usual.
> it isn't gone. so i do org-clock-cancel,
recent maint.
just wondering what i could be doing wrong.
it is /usually/ the case that i get clock start tmie is gone when i
try to clock out.
it isn't gone. so i do org-clock-cancel, which is slow. this leaves
the start time.
so i do org-clock-in, which presents me with all the options. i
Noah Slater nslater at apache.org writes:
I'm moving point over a habit in the agenda, clocking on with I,
switching buffer a few times, then switching back and hitting O.
Occasionally, I get a Clock start time is gone message. I just got
one now. If I go to the node, I see this:
:LOGBOOK:
Hello,
I'm moving point over a habit in the agenda, clocking on with I,
switching buffer a few times, then switching back and hitting O.
Occasionally, I get a Clock start time is gone message. I just got
one now. If I go to the node, I see this:
:LOGBOOK:
CLOCK: [2014-09-07 Sun 19:41]
- State
15 matches
Mail list logo