From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org
Subject: org-clock-in fails sometimes with prefix arg
Date: Wed, 19 Nov 2008 11:25:08 -0500 [thread overview]
Message-ID: <87ljvfznrv.fsf@gollum.intra.norang.ca> (raw)
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
next reply other threads:[~2008-11-19 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 16:25 Bernt Hansen [this message]
2008-11-20 7:26 ` org-clock-in fails sometimes with prefix arg Carsten Dominik
2008-11-20 13:56 ` Bernt Hansen
2008-11-20 14:40 ` Bernt Hansen
2008-11-20 14:46 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ljvfznrv.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).