From: Dave Abrahams <dave@boostpro.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Resilience to leaving Emacs w/o clocking out [7.02trans]
Date: Mon, 1 Nov 2010 21:07:02 -0400 [thread overview]
Message-ID: <AANLkTinvbR3LadEd1go4DV9a9aHGuMXsik6KtmXWCF--@mail.gmail.com> (raw)
In-Reply-To: <D5F77EF4-031F-4DBE-97F0-FD6C5BFC39DB@gmail.com>
On Mon, Nov 1, 2010 at 3:39 PM, Carsten Dominik
<carsten.dominik@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
next prev parent reply other threads:[~2010-11-02 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 14:56 Bug: Resilience to leaving Emacs w/o clocking out [7.02trans] David Abrahams
2010-11-01 19:39 ` Carsten Dominik
2010-11-02 1:07 ` Dave Abrahams [this message]
2010-11-04 14:45 ` Sébastien Vauban
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=AANLkTinvbR3LadEd1go4DV9a9aHGuMXsik6KtmXWCF--@mail.gmail.com \
--to=dave@boostpro.com \
--cc=carsten.dominik@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).