emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: BUG REPORT - problem with org.elc on clocking out
Date: Mon, 10 Aug 2015 14:04:56 -0400	[thread overview]
Message-ID: <87pp2vnho7.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87h9o7oxhn.fsf@skimble.plus.com

Sharon Kimble <boudiccas@skimble.plus.com> writes:

> Kyle Meyer <kyle@kyleam.com> writes:
>
>> Do you still get the error after running 'C-u M-x org-reload'?
>>
> Yes, its still occurring even after closing and restarting emacs. In
> fact I've just done this to check for certain, and this time it threw up
> a debugger page, which says -
>

The backtrace *may* be enough for somebody to debug but FYI: C-u M-x org-reload
reloads *uncompiled* org-mode which makes the backtrace much more
informative.

> Debugger entered--Lisp error: (wrong-number-of-arguments #[(pos) "r\302\b!\203\303\b!\202pq\210\212\214~\210\bb\210\304 \305	!\306>\205=\307\310	\"?\205=\307\311	\"\307\312	\"b\210\313\314x\210\314y\210`|,\207" [pos drawer markerp marker-buffer org-element-at-point org-element-type (drawer property-drawer) org-element-property :contents-begin :begin :end " 	
> " nil] 4 ("/home/boudiccas/.emacs.d/elpa/org-plus-contrib-20150805/org.elc" . 462364)] 2)
>   org-remove-empty-drawer-at("LOGBOOK" 11266)
>   (save-excursion (beginning-of-line 0) (org-remove-empty-drawer-at "LOGBOOK" (point)))
>   bh/remove-empty-drawer-on-clock-out()
>   #[(f) "\b \207" [f] 1](bh/remove-empty-drawer-on-clock-out)
>   mapc(#[(f) "\b \207" [f] 1] (org-clock-remove-empty-clock-drawer bh/remove-empty-drawer-on-clock-out bh/clock-out-maybe))
>   byte-code("\306 \204\x1f\307\310\b\"	\311 \210\v\203\312\313\314\"\210\202\x1f\315\316!\210\f\2035\317\320r\321!q\210@)\322\314\323%\2027A\324B!\322\211\211\211\211\211CDEFGHIAIJ\212\325 q\210\214~\210b\210\326\327!\210\330\331KP!\203~\332\327!L\232\203~\332\333!H\202\216\v\203\212\312\313\322\"\210\202\216\334\335!\210\336\225b\210`\337 |\210\340c\210\341M\206\242I\342\343#G\344\345\346\347G!\"!\344\345\346\347H!\"!ZF\350F\351\245!EFE\351_ZF\350F\352\245!DF\211\352_ZF\353\354\355ED#\261\210N\205\364ED\\\336U\211C\203\326\327!\210`\337 |\210\330\356!\203d`TV\203\357\327!\210\322\211\223\210O\322\211\223\210P\2033\360\361\322\211\211\211\362\363\314!\364Q&\210Q\203@\365Q!\210\322QR\203M\365R!\210\322R\307\310\b\"	A\203\234\212\366\314!\210\314\322ST\367A!\203\205\330U!\210A\332\333!!\211V\203\201\370V!\210)\202\233A\203\233\330W\331A\371R!\204\233\370A!\210+\311 \210\372\373\374E\352_D\\!\375QGC\203\267\376\202\270\377#\210X\201\\ YEY\203\355Y;\204\355\201] \203\355Z\201^=\203\355S\203\355\307\201_E\"E\201`\201aE\"\210*\306 ?\205\322\211[.\n\207" [global-mode-string org-frame-title-format-backup frame-title-format fail-quietly switch-to-state org-clock-marker org-clocking-p delq org-mode-line-string force-mode-line-update throw exit t user-error "No active clock" completing-read "Switch to state: " marker-buffer nil "DONE" org-current-time org-clocking-buffer beginning-of-line 1 looking-at "[ 	]*" match-string 2 error "Clock start time is gone" 0 point-at-eol "--" org-insert-time-stamp with-hm inactive org-float-time apply encode-time org-parse-time-string floor 3600 60 " => " format "%2d:%02d" "\n" delete-char org-add-log-setup clock-out ...] 10)
>   org-clock-out()
>   org-agenda-clock-out()
>   #<subr call-interactively>(org-agenda-clock-out nil nil)
>   ad-Advice-call-interactively(#<subr call-interactively> org-agenda-clock-out nil nil)
>   apply(ad-Advice-call-interactively #<subr call-interactively> (org-agenda-clock-out nil nil))
>   call-interactively(org-agenda-clock-out nil nil)
>   command-execute(org-agenda-clock-out)
>

A backtrace produced with uncompiled code would have lisp code instead
of the byte-code binary stuff.

Nick

  parent reply	other threads:[~2015-08-10 18:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 20:00 BUG REPORT - problem with org.elc on clocking out Sharon Kimble
2015-08-09 20:30 ` Kyle Meyer
2015-08-10 17:37   ` Sharon Kimble
2015-08-10 17:54     ` Kyle Meyer
2015-08-10 18:23       ` Achim Gratz
2015-08-10 18:28       ` Sharon Kimble
2015-08-10 18:38         ` Kyle Meyer
2015-08-10 18:04     ` Nick Dokos [this message]
2015-08-10 21:33     ` Nicolas Goaziou
2015-08-11 20:12       ` Sharon Kimble

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=87pp2vnho7.fsf@alphaville.usersys.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).