Re: org-clock-in fails sometimes with prefix arg

From: Carsten Dominik <dominik@science.uva.nl>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clock-in fails sometimes with prefix arg
Date: Thu, 20 Nov 2008 15:46:51 +0100	[thread overview]
Message-ID: <C73CA9EA-CD6C-4A53-A71A-03A9D0235183@uva.nl> (raw)
In-Reply-To: <87vduibgvh.fsf@gollum.intra.norang.ca>

OK, thanks, I'll wait with actions for more info.

- Carsten

On Nov 20, 2008, at 3:40 PM, Bernt Hansen wrote:

> This happened again this morning.  I'm not (to my knowledge) actually
> using the org-clock-persistence stuff but it is active.  Again I  
> have an
> 'org' buffer which is a dired entry at the end of my clock history  
> list.
>
> I'm going to try a few things
>
>  - restart emacs and see if I can reproduce what causes this
>
>  - turn off the cock persistence settings and see if this problem goes
>    away (don't expect a report on that for at least a week)
>
> -Bernt
>
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> Hi Bernt,
>>
>> are you saving clock information from session to session,
>> using org-clock-persistence-insinuate?
>>
>> - Carsten
>> On Nov 19, 2008, at 5:25 PM, Bernt Hansen wrote:
>>
>>    Hi Carsten,
>>
>>    I've run into this a few times today.  I don't have any useful  
>> insight
>>
>>    into how this occurs yet but I thought I'd mention it anyway.
>>
>>    My current org-clock-history looks like this:
>>
>>    ,----[ C-h v org-clock-history RET]
>>
>>    | org-clock-history is a variable defined in `org-clock.el'.
>>
>>    | Its value is
>>
>>    | (#<marker at 5990 in norang.org> #<marker at 42510 in  
>> norang.org> #
>>    <marker at 8870 in csp.org> #<marker at 6269 in org.org>  
>> #<marker at 5145
>>    in ciss.org> #<marker at 339 in org> #<marker at 1 in org>  
>> #<marker at
>>    10546 in csp.org> #<marker at 9659 in csp.org> #<marker at 10794  
>> in
>>    csp.org>)
>>
>>    |
>>
>>    |
>>
>>    |
>>
>>    | Documentation:
>>
>>    | List of marker pointing to recent clocked tasks.
>>
>>    `----
>>
>>    Somehow I am getting markers to read-only buffers in there
>>
>>    eg.    (#<marker at 1 in org>)
>>
>>    and this breaks C-u M-x org-clock-in which triggers the  
>> following error
>>
>>    in org-clock-select-task
>>
>>    ,----
>>
>>    | save-restriction: Buffer is read-only: #<buffer org>
>>
>>    `----
>>
>>    I'm not sure how I got these markers in the list
>>
>>    org-clock-select-task fails when it hits the read-only buffer.   
>> This org
>>
>>    buffer happens to be a directory (in dired I believe) of my ~/ 
>> git/org
>>
>>    directory.
>>
>>    As a workaround for now I'm just manually clearing the variable  
>> with
>>
>>    (setq org-clock-history nil)
>>
>>    to remove the markers and make this work again.
>>
>>    Regards,
>>
>>    Bernt
>>
>>    _______________________________________________
>>
>>    Emacs-orgmode mailing list
>>
>>    Remember: use `Reply All' to send replies to the list.
>>
>>    Emacs-orgmode@gnu.org
>>
>>    http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode