emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
To: Joseph Thomas <six50joe@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Cc: Bernt Hansen <bernt@norang.ca>
Subject: Re: Feature that org mode needs most
Date: Wed, 18 Jul 2012 09:50:49 +0100 (BST)	[thread overview]
Message-ID: <1342601449.87301.YahooMailNeo@web29806.mail.ird.yahoo.com> (raw)
In-Reply-To: <CA+1iLPB5_jwFEchhysNESmK9E82t4Eni_k44hUHLztHTGpsm0g@mail.gmail.com>



Hi, Joseph,
(I cc'ed also Bernt Hansen, aka "the king of clocking" ;-)
maybe he has better ideas; he's more experience than me, for sure ;)


Da: Joseph Thomas <six50joe@gmail.com>
Inviato: Martedì 17 Luglio 2012 23:15

> there's no easy way I can see to make quick adjustments to clocked time between activities.  

> Every day I will forget to clock to a new activity at some point.  

> By the time I remember, time has passed.  For example, I come back from a meeting and begin to work on a project. 

>  20 minutes into it, I clock in. 

>  But I must then manually adjust both the previous activity and the current one so that they are accurate and don't overlap in the agenda view.  


When you can back from a meeting you can resolve idel time
    [[info:org#Resolving%20idle%20time][info:org#Resolving idle time]]


If you changed your task but you forgot to clock outyou should check:

[[info:org#Clocking%20commands][info:org#Clocking commands]]

 (`org-clock-in-last')'
     Reclock the last clocked task.  With one `C-u' prefix argument,
     select the task from the clock history.  With two `C-u' prefixes,
     force continuous clocking by starting the clock when the last clock
     stopped.


Be careful to have a recent git version since this is a new feature, but it had bugs and
the bugs have been fixed.


Other thoughts:

You can change the time from the agenda (never tried) but:

[[info:org#Agenda%20commands][info:org#Agenda commands]]
`v c'
     Show overlapping clock entries, clocking gaps, and other clocking
     problems in the current agenda range.  You can then visit clocking
     lines and fix them manually.  See the variable
     `org-agenda-clock-consistency-checks' for information on how to
     customize the definition of what constituted a clocking problem.
     To return to normal agenda display, press `l' to exit Logbook mode.


Finally you can also use the brute force method:
clock in the new task   

then run 

M-x org-resolve-clocks


so that you can "restart" your current task by, say, 20 minutes
then you can set 


(defcustom org-clock-out-remove-zero-time-clocks t
  "Non-nil means remove the clock line when the resulting time is zero."
  :group 'org-clock
  :type 'boolean)

However the last clocked-out task (the meeting) has been clocked out 20 minutes later.

cheers,
Giovanni


  parent reply	other threads:[~2012-07-18  8:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 21:15 Feature that org mode needs most Joseph Thomas
2012-07-17 21:33 ` Mehul Sanghvi
2012-07-18  9:03   ` Rainer Stengele
2012-08-01 12:59   ` Steinar Bang
2012-08-01 13:21     ` Bastien
2012-08-01 14:05       ` Sebastien Vauban
2012-08-01 14:08         ` Bastien
2012-08-01 16:39       ` Steinar Bang
2012-08-02 15:13         ` Bastien
2012-08-15 12:38           ` Steinar Bang
2012-08-15 19:09             ` Bastien
2012-08-16 13:01               ` Steinar Bang
2012-08-19  7:30                 ` Bastien
2012-08-21  7:33                   ` Steinar Bang
2012-08-21 18:10                     ` Bastien
2012-07-18  8:50 ` Giovanni Ridolfi [this message]
2012-07-18 14:01   ` Joseph Thomas
2012-07-18 15:46     ` Giovanni Ridolfi
2012-07-18 15:51       ` Joseph Thomas
2012-07-18 18:26         ` John Hendy
2012-07-19 14:00           ` Giovanni Ridolfi
2012-07-27 23:27     ` Bastien
2012-07-18 14:06   ` Joseph Thomas
2012-07-20  7:34     ` Giovanni Ridolfi
2012-07-27 23:25     ` Bastien

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=1342601449.87301.YahooMailNeo@web29806.mail.ird.yahoo.com \
    --to=giovanni.ridolfi@yahoo.it \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=six50joe@gmail.com \
    /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).