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 08:26:50 +0100 Message-ID: References: <87ljvfznrv.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v929.2) Content-Type: multipart/mixed; boundary="===============1569091330==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L33wF-0002Am-JJ for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 02:26:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L33wE-0002AS-OY for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 02:26:55 -0500 Received: from [199.232.76.173] (port=45913 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L33wE-0002AM-Im for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 02:26:54 -0500 Received: from ug-out-1314.google.com ([66.249.92.172]:27852) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L33wE-0000Zr-3y for emacs-orgmode@gnu.org; Thu, 20 Nov 2008 02:26:54 -0500 Received: by ug-out-1314.google.com with SMTP id 36so219586uga.17 for ; Wed, 19 Nov 2008 23:26:53 -0800 (PST) In-Reply-To: <87ljvfznrv.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 --===============1569091330== Content-Type: multipart/alternative; boundary=Apple-Mail-11--249292199 --Apple-Mail-11--249292199 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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 > | (# # > # # # at 5145 in ciss.org> # # > # # # 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. (#) > > 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 --Apple-Mail-11--249292199 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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

= --Apple-Mail-11--249292199-- --===============1569091330== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============1569091330==--