[Orgmode] Bug: Resilience to leaving Emacs w/o clocking out [7.02trans]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
I wrote this to John W:
Somehow I ended up with this in todo.txt:
*** DONE [#A] Check in elisp state
SCHEDULED: 2010-10-31 Sun
:LOGBOOK:
CLOCK: [2010-10-31 Sun 13:31]
CLOCK: [2010-10-21 Thu 12:01]--[2010-10-21 Thu 16:43] = 4:42
:END:
:PROPERTIES:
:Link: [[file:~/elisp/package.d/wl-gravatar.el::]]
:ID: A661E17F-4526-4BBB-B8E7-43651123C472
:END:
[2010-10-12 Tue 10:05]
As a result, when I fired up emacs, it would always tell me there was a
dangling clock, but I couldn't clock out, even by `j M-x org-clock-out'.
Eventually I figured out to use J and it got cleaned up, but I'm still
a bit baffled about how I ended up in this condition.
and he replied:
This happens for me if I exit Emacs without clocking out first.
Seems like a bug.
Emacs : GNU Emacs 23.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.29)
of 2010-05-08 on black.local
Package: Org-mode version 7.02trans
current state:
==
(setq
org-agenda-deadline-leaders '(D: D%d: )
org-clock-in-switch-to-state STARTED
org-agenda-skip-scheduled-if-deadline-is-shown t
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-todo-keyword-faces '((TODO :foreground medium blue :weight bold)
(APPT :foreground medium blue :weight bold)
(NOTE :foreground brown :weight bold) (STARTED
:foreground dark orange :weight bold)
(WAITING :foreground red :weight bold)
(DELEGATED :foreground dark violet :weight bold)
(DEFERRED :foreground dark blue :weight bold)
(SOMEDAY :foreground dark blue :weight bold)
(PROJECT :height 1.5 :weight bold :foreground
black))
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-custom-commands '((E Errands (next 3 days) tags
ErrandTODO\DONE\TODO\CANCELLED\STYLE\habit\SCHEDULED\+3d\
((org-agenda-overriding-header Errands (next 3
days
(A Priority #A tasks agenda
((org-agenda-ndays 1)
(org-agenda-overriding-header Today's priority #A tasks: )
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote
notregexp) \\=.*\\[#A\\])))
)
)
(B Priority #A and #B tasks agenda
((org-agenda-ndays 1)
(org-agenda-overriding-header Today's priority #A and #B tasks: )
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote
regexp) \\=.*\\[#C\\])))
)
)
(w Waiting/delegated tasks tags
TODO=\WAITING\|TODO=\DELEGATED\
((org-agenda-overriding-header
Waiting/delegated tasks:)
(org-agenda-sorting-strategy (quote
(todo-state-up priority-down category-up
)
(u Unscheduled tasks tags
TODO\\TODO\DONE\TODO\CANCELLED\TODO\NOTE\CATEGORY{CEG\\|ABC\\|Bizcard\\|Adagio\\|EVAprint\\|\\IT\\}
((org-agenda-overriding-header Unscheduled
tasks: )
(org-agenda-skip-function
(quote
Re: [Orgmode] Bug: Resilience to leaving Emacs w/o clocking out [7.02trans]
On Nov 1, 2010, at 3:56 PM, David Abrahams wrote:
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report?
See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
I wrote this to John W:
Somehow I ended up with this in todo.txt:
*** DONE [#A] Check in elisp state
SCHEDULED: 2010-10-31 Sun
:LOGBOOK:
CLOCK: [2010-10-31 Sun 13:31]
CLOCK: [2010-10-21 Thu 12:01]--[2010-10-21 Thu 16:43] = 4:42
:END:
:PROPERTIES:
:Link: [[file:~/elisp/package.d/wl-gravatar.el::]]
:ID: A661E17F-4526-4BBB-B8E7-43651123C472
:END:
[2010-10-12 Tue 10:05]
As a result, when I fired up emacs, it would always tell me there
was a
dangling clock, but I couldn't clock out, even by `j M-x org-clock-
out'.
Eventually I figured out to use J and it got cleaned up, but I'm
still
a bit baffled about how I ended up in this condition.
and he replied:
This happens for me if I exit Emacs without clocking out first.
Seems like a bug.
No, this is meant to work like this. Next time you start up Emacs,
you get a chance to fix this clock. What would you like to happen?
That you always clock out when you exit Emacs?
- Carsten
Emacs : GNU Emacs 23.2.1 (x86_64-apple-darwin, NS apple-
appkit-1038.29)
of 2010-05-08 on black.local
Package: Org-mode version 7.02trans
current state:
==
(setq
org-agenda-deadline-leaders '(D: D%d: )
org-clock-in-switch-to-state STARTED
org-agenda-skip-scheduled-if-deadline-is-shown t
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-
vars)
org-todo-keyword-faces '((TODO :foreground medium blue :weight
bold) (APPT :foreground medium blue :weight bold)
(NOTE :foreground brown :weight bold)
(STARTED :foreground dark orange :weight bold)
(WAITING :foreground red :weight bold)
(DELEGATED :foreground dark violet :weight bold)
(DEFERRED :foreground dark blue :weight
bold)
(SOMEDAY :foreground dark blue :weight
bold)
(PROJECT :height 1.5 :weight
bold :foreground black))
org-speed-command-hook '(org-speed-command-default-hook org-babel-
speed-command-hook)
org-agenda-custom-commands '((E Errands (next 3 days) tags
ErrandTODO\DONE\TODO
\CANCELLED\STYLE\habit\SCHEDULED\+3d\
((org-agenda-overriding-header
Errands (next 3 days
(A Priority #A tasks agenda
((org-agenda-ndays 1) (org-agenda-
overriding-header Today's priority #A tasks: )
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if
(quote notregexp) \\=.*\\[#A\\])))
)
)
(B Priority #A and #B tasks agenda
((org-agenda-ndays 1) (org-agenda-
overriding-header Today's priority #A and #B tasks: )
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if
(quote regexp) \\=.*\\[#C\\])))
)
)
(w Waiting/delegated tasks tags
TODO=\WAITING\|TODO=\DELEGATED\
((org-agenda-overriding-header
Waiting/delegated tasks:)
(org-agenda-sorting-strategy (quote
(todo-state-up priority-down category-up
)
(u Unscheduled tasks tags
TODO\\TODO\DONE\TODO
\CANCELLED\TODO\NOTE\CATEGORY{CEG\\|ABC\\|Bizcard\\|Adagio\
\|EVAprint\\|\\IT\\}
((org-agenda-overriding-header
Unscheduled tasks: )
(org
-agenda-skip-function
(quote
(org
-agenda-skip-entry-if
(quote
scheduled)
Re: [Orgmode] Bug: Resilience to leaving Emacs w/o clocking out [7.02trans]
On Mon, Nov 1, 2010 at 3:39 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On Nov 1, 2010, at 3:56 PM, David Abrahams wrote: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. I wrote this to John W: Somehow I ended up with this in todo.txt: *** DONE [#A] Check in elisp state SCHEDULED: 2010-10-31 Sun :LOGBOOK: CLOCK: [2010-10-31 Sun 13:31] CLOCK: [2010-10-21 Thu 12:01]--[2010-10-21 Thu 16:43] = 4:42 :END: :PROPERTIES: :Link: [[file:~/elisp/package.d/wl-gravatar.el::]] :ID: A661E17F-4526-4BBB-B8E7-43651123C472 :END: [2010-10-12 Tue 10:05] As a result, when I fired up emacs, it would always tell me there was a dangling clock, but I couldn't clock out, even by `j M-x org-clock-out'. Eventually I figured out to use J and it got cleaned up, but I'm still a bit baffled about how I ended up in this condition. and he replied: This happens for me if I exit Emacs without clocking out first. Seems like a bug. No, this is meant to work like this. Next time you start up Emacs, you get a chance to fix this clock. What would you like to happen? That you always clock out when you exit Emacs? No, I expected that I'd at least be *able* to clock out with `M-x org-clock-out' after I start Emacs back up. -- Dave Abrahams BoostPro Computing http://www.boostpro.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
