From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: org-clock-in fails sometimes with prefix arg Date: Thu, 20 Nov 2008 15:46:51 +0100 Message-ID: References: <87ljvfznrv.fsf@gollum.intra.norang.ca> <87vduibgvh.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v929.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L3Ao5-0000C4-DG for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 09:46:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L3Ao4-0000BH-Lh for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 09:46:57 -0500 Received: from [199.232.76.173] (port=40367 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L3Ao4-0000B0-FH for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 09:46:56 -0500 Received: from nf-out-0910.google.com ([64.233.182.190]:41821) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L3Ao3-0001ms-W8 for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 09:46:56 -0500 Received: by nf-out-0910.google.com with SMTP id c7so275805nfi.26 for ; Thu, 20 Nov 2008 06:46:54 -0800 (PST) In-Reply-To: <87vduibgvh.fsf@gollum.intra.norang.ca> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bernt Hansen Cc: emacs-orgmode@gnu.org 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 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 >> >> | (# #> norang.org> # >> # >> #> in ciss.org> # # >> #> 10546 in csp.org> # #> in >> csp.org>) >> >> | >> >> | >> >> | >> >> | Documentation: >> >> | List of marker pointing to recent clocked tasks. >> >> `---- >> >> Somehow I am getting markers to read-only buffers in there >> >> eg. (#) >> >> 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: # >> >> `---- >> >> 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