emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Something like 'org-clock-in-at-time'?
Date: Sun, 13 Mar 2011 18:05:38 -0700	[thread overview]
Message-ID: <87zkoyv7dp.fsf@berkeley.edu> (raw)
In-Reply-To: AANLkTimXSpT8j5rf=KYpi32rLtmppLO9t8TRKA_5MSr9@mail.gmail.com

John Hendy <jw.hendy@gmail.com> writes:

> Could someone fill me in on your process for clocking in things after
> the fact? I've been trying to get into to clocking, but, especially at
> home, I don't return to my computer in between every different thing.
> Instead, I stop at it when I get a pause and try to fill in what I've
> been doing. So far, this has been something akin to:
> - create a new sub-headline and call it what I was doing
> - C-c C-c to tag it
> - C-c C-x C-i followed by C-c C-x C-o to create a clocked time stamps
> - Manually edit the times
> - C-c C-c to update the count

Not sure if this is entirely relevant here, but I have a similar
problem.  I often find I need to mark recurring tasks as "done" that I
completed on the previous day or even earlier.  For most tasks, it
doesn't matter when I mark them as done; but if the task uses org-habits, it
means I have to manually edit the timestamp so that it doesn't mess up
the habit log going forward.

If there's a better way to deal with situations like this, I'd love to
hear about it.  If not, I just wanted to point out another use case for
anyone thinking about implementing "retroactive timestamp editing"



  reply	other threads:[~2011-03-14  1:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 20:48 Something like 'org-clock-in-at-time'? John Hendy
2011-03-14  1:05 ` Richard Lawrence [this message]
2011-04-09 17:24 ` John Hendy
2011-04-09 18:03   ` Bernt Hansen
2011-04-09 18:05     ` Bernt Hansen
2011-04-10 15:00     ` John Hendy
2011-04-10 16:32       ` Bernt Hansen
2011-04-11  0:59         ` John Hendy
2011-04-11  2:42     ` Nathan Neff

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:

  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=87zkoyv7dp.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --cc=emacs-orgmode@gnu.org \


* 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


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).