From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: clock-in clock-out problems
Date: Mon, 18 Aug 2014 17:39:06 -0400 [thread overview]
Message-ID: <87d2bxpjet.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: lstp8f$60d$1@ger.gmane.org
hymie@lactose.homelinux.net (hymie!) writes:
>>> (lines cut to 75-ish, but I can try to send the full entire error message
>>> if needed)
>>>
>>> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
>>> goto-char(nil)
>>> (cond ((and org-clock-in-resume (looking-at (concat "^[ ]*" org-cloc
>>> (save-restriction (widen) (goto-char target-pos) (org-back-to-heading t) (
>>> (save-excursion (save-restriction (widen) (goto-char target-pos) (org-back
>>> (save-excursion (if (and selected-task (marker-buffer selected-task)) (pro
>>> (let ((interrupting (and (not org-clock-resolving-clocks-due-to-idleness)
>>> (catch (quote abort) (let ((interrupting (and (not org-clock-resolving-clo
>>> org-clock-in()
>>> [...]
>>
>>I added the following to my .emacs
>>
>>--8<---------------cut here---------------start------------->8---
>>(require 'org-clock)
>>(setq org-clock-persist t)
>>(org-clock-persistence-insinuate)
>>--8<---------------cut here---------------end--------------->8---
>
> I didn't have (require 'org-clock) ; just added it; no help.
>
>>If you get an error, then it might be a bug in your version. Post the
>>version along with the complete backtrace (preferably using
>>org-submit-bug-report).
>
> The entry that I'm using is just
>
> * TODO clock test
> CLOCK: [2014-08-18 Mon 16:20]
>
> (This is the "Messages" that you asked for in the other post)
>
> ("emacs" "zz.org")
> For information about GNU Emacs and the GNU system, type C-x h C-a.
> Restoring clock data
> Loading /home/hymie/.emacs.d/org-clock-save.el (source)...done
> Resume clock (clock test) (y or n) y
> Matched 2014-08-18 Mon 16:20
> Entering debugger...
> Quit
>
... and the complete backtrace? Does it look like the partial one
you posted before? In particular, is the argument to goto-char nil?
If that's the case, and assuming I'm in the right place in the source
code, *Messages* shows the correct value for the matched string but the
backtrace shows that match-end returned nil which means that the regexp
*did not match*. Both of these two cannot be right (unless there is a bug
in the emacs regexp matching code, which for now at least, I'm
discounting).
--
Nick
next prev parent reply other threads:[~2014-08-18 21:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 15:40 clock-in clock-out problems hymie!
2014-08-18 18:26 ` Joost Helberg
2014-08-18 19:02 ` hymie!
2014-08-18 20:10 ` Nick Dokos
2014-08-18 20:18 ` Nick Dokos
2014-08-18 20:55 ` hymie!
2014-08-18 21:39 ` Nick Dokos [this message]
2014-08-19 3:23 ` hymie!
2014-08-19 15:01 ` hymie!
2014-08-19 15:51 ` Nick Dokos
2014-08-19 18:21 ` hymie!
2014-08-19 20:46 ` hymie!
2014-08-19 22:42 ` Nick Dokos
2014-08-22 13:55 ` Bastien
2014-08-19 7:55 ` Sebastien Vauban
2014-08-19 12:32 ` Nick Dokos
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=87d2bxpjet.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.com \
--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).