emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] BUG REPORT - problem with org.elc on clocking out


From: Nick Dokos
Subject: Re: [O] BUG REPORT - problem with org.elc on clocking out
Date: Mon, 10 Aug 2015 14:04:56 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Sharon Kimble <address@hidden> writes:

> Kyle Meyer <address@hidden> 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!\203\303!\202pq\210\212\214~\210b\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) " \207" [f] 1](bh/remove-empty-drawer-on-clock-out)
>   mapc(#[(f) " \207" [f] 1] (org-clock-remove-empty-clock-drawer 
> bh/remove-empty-drawer-on-clock-out bh/clock-out-maybe))
>   byte-code("\306 \204\307\310\"    \311 
> \210\203\312\313\314\"\210\202\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\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&address@hidden"
>     
> 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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]