Forgot to ask in my last response- since I plan to use org-resolve-clocks
much more regularly than perhaps it was intended, I would like to make a
key biniding for it.  If there are plans to do this in an emacs
distribution at some point, I'd like to choose something logical- ideally
something that the org team would choose.  Could you make a suggestion?

Thanks again!
Joe

On Wed, Jul 18, 2012 at 4:50 AM, Giovanni Ridolfi <giovanni.ridolfi@yahoo.it
> wrote:

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