From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug: Resilience to leaving Emacs w/o clocking out [7.02trans]
Date: Thu, 04 Nov 2010 15:45:50 +0100 [thread overview]
Message-ID: <80aalp87vl.fsf@mundaneum.com> (raw)
In-Reply-To: AANLkTinvbR3LadEd1go4DV9a9aHGuMXsik6KtmXWCF--@mail.gmail.com
Hi Dave and Carsten,
Dave Abrahams wrote:
> On Mon, Nov 1, 2010 at 3:39 PM, Carsten Dominik
>> On Nov 1, 2010, at 3:56 PM, David Abrahams wrote:
>>>> 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.
The only thing that could make sense is something that was (more or less?)
standard with Planner: overriding =kill-emacs= (=C-c C-x=) in order to ask you
if you want to clock out before leaving Emacs, if you still have a running
clock.
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-11-04 14:45 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
2010-11-04 14:45 ` Sébastien Vauban [this message]
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=80aalp87vl.fsf@mundaneum.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).