From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joseph Thomas Subject: Re: Feature that org mode needs most Date: Wed, 18 Jul 2012 10:06:18 -0400 Message-ID: References: <1342601449.87301.YahooMailNeo@web29806.mail.ird.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b343b52b8708204c51b2a89 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36520) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SrUtV-0004j6-HY for emacs-orgmode@gnu.org; Wed, 18 Jul 2012 10:06:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SrUtP-00057f-FQ for emacs-orgmode@gnu.org; Wed, 18 Jul 2012 10:06:25 -0400 Received: from mail-ee0-f41.google.com ([74.125.83.41]:45516) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SrUtP-00057Y-17 for emacs-orgmode@gnu.org; Wed, 18 Jul 2012 10:06:19 -0400 Received: by eekc50 with SMTP id c50so623366eek.0 for ; Wed, 18 Jul 2012 07:06:18 -0700 (PDT) In-Reply-To: <1342601449.87301.YahooMailNeo@web29806.mail.ird.yahoo.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Giovanni Ridolfi Cc: Bernt Hansen , "emacs-orgmode@gnu.org" --047d7b343b52b8708204c51b2a89 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 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 > Inviato: Marted=EC 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 vie= w. > > > 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 > > --047d7b343b52b8708204c51b2a89 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Forgot to ask in my last response- since I plan to use org-resolve-clocks m= uch more regularly than perhaps it was intended, I would like to make a key= biniding for it. =A0If 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. =A0Could you make a suggestion?

Thanks again!
Joe

On Wed, Jul 18, 2012 at 4:50 AM, Giovanni Ridolfi <<= a href=3D"mailto:giovanni.ridolfi@yahoo.it" target=3D"_blank">giovanni.rido= lfi@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=EC 17 Luglio 2012 23:15

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

> Every day I will forget to clock to a new activity at some point.=A0
> By the time I remember, time has passed. =A0For example, I come back f= rom a meeting and begin to work on a project.

>=A0 20 minutes into it, I clock in.

>=A0 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 v= iew.=A0


When you can back from a meeting you can resolve idel time
=A0=A0=A0 [[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]]

=A0(`org-clock-in-last')'
=A0=A0=A0=A0 Reclock the last clocked task.=A0 With one `C-u' prefix ar= gument,
=A0=A0=A0=A0 select the task from the clock history.=A0 With two `C-u' = prefixes,
=A0=A0=A0=A0 force continuous clocking by starting the clock when the last = clock
=A0=A0=A0=A0 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'
=A0=A0=A0=A0 Show overlapping clock entries, clocking gaps, and other clock= ing
=A0=A0=A0=A0 problems in the current agenda range.=A0 You can then visit cl= ocking
=A0=A0=A0=A0 lines and fix them manually.=A0 See the variable
=A0=A0=A0=A0 `org-agenda-clock-consistency-checks' for information on h= ow to
=A0=A0=A0=A0 customize the definition of what constituted a clocking proble= m.
=A0=A0=A0=A0 To return to normal agenda display, press `l' to exit Logb= ook mode.


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

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
=A0 "Non-nil means remove the clock line when the resulting time is ze= ro."
=A0 :group 'org-clock
=A0 :type 'boolean)

However the last clocked-out task (the meeting) has been clocked out 20 min= utes later.

cheers,
Giovanni


--047d7b343b52b8708204c51b2a89--