org-clock-in
) ¶Start the clock on the current item (clock-in). This inserts the
‘CLOCK’ keyword together with a timestamp. If this is not the first
clocking of this item, the multiple ‘CLOCK’ lines are wrapped into
a ‘LOGBOOK’ drawer (see also the variable org-clock-into-drawer
).
You can also overrule the setting of this variable for a subtree by
setting a ‘CLOCK_INTO_DRAWER’ or ‘LOG_INTO_DRAWER’ property. When
called with a C-u prefix argument, select the task from
a list of recently clocked tasks. With two C-u C-u
prefixes, clock into the task at point and mark it as the default
task; the default task is always be available with letter
d when selecting a clocking task. With three C-u C-u C-u prefixes, force continuous clocking by starting the
clock when the last clock stopped.
While the clock is running, Org shows the current clocking time in
the mode line, along with the title of the task. The clock time
shown is all time ever clocked for this task and its children. If
the task has an effort estimate (see Effort Estimates), the
mode line displays the current clocking time against it73. If the task is a repeating one (see
Repeated tasks), show only the time since the last reset of the
task74. You can exercise more control over show
time with the ‘CLOCK_MODELINE_TOTAL’ property. It may have the
values ‘current’ to show only the current clocking instance, ‘today’
to show all time clocked on this tasks today—see also the variable
org-extend-today-until
, all
to include all time, or auto
which
is the default75. Clicking with mouse-1
onto the mode line entry pops up a menu with clocking options.
org-clock-out
) ¶Stop the clock (clock-out). This inserts another timestamp at the
same location where the clock was last started. It also directly
computes the resulting time in inserts it after the time range as
‘=>HH:MM’. See the variable org-log-note-clock-out
for the
possibility to record an additional note together with the clock-out
timestamp76.
org-clock-in-last
) ¶Re-clock 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.
org-clock-modify-effort-estimate
) ¶Update the effort estimate for the current clock task.
org-evaluate-time-range
) ¶Recompute the time interval after changing one of the timestamps. This is only necessary if you edit the timestamps directly. If you change them with S-<cursor> keys, the update is automatic.
org-clock-timestamps-up
) ¶org-clock-timestamps-down
)On CLOCK log lines, increase/decrease both timestamps so that the clock duration keeps the same value.
org-timestamp-up
) ¶org-timestamp-down
)On ‘CLOCK’ log lines, increase/decrease the timestamp at point and the one of the previous, or the next, clock timestamp by the same duration. For example, if you hit S-M-UP to increase a clocked-out timestamp by five minutes, then the clocked-in timestamp of the next clock is increased by five minutes.
org-todo
) ¶Changing the TODO state of an item to DONE automatically stops the clock if it is running in this same item.
org-clock-cancel
) ¶Cancel the current clock. This is useful if a clock was started by mistake, or if you ended up working on something else.
org-clock-goto
) ¶Jump to the headline of the currently clocked in task. With a C-u prefix argument, select the target task from a list of recently clocked tasks.
org-clock-display
) ¶Display time summaries for each subtree in the current buffer. This
puts overlays at the end of each headline, showing the total time
recorded under that heading, including the time of any subheadings.
You can use visibility cycling to study the tree, but the overlays
disappear when you change the buffer (see variable
org-remove-highlights-with-change
) or press C-c C-c.
The l key may be used in the agenda (see Weekly/daily agenda) to show which tasks have been worked on or closed during a day.
Important: note that both org-clock-out
and org-clock-in-last
can have a global keybinding and do not modify the window disposition.
To add
an effort estimate “on the fly”, hook a function doing this to
org-clock-in-prepare-hook
.
The last reset of the task is recorded by the ‘LAST_REPEAT’ property.
See also the variable
org-clock-mode-line-total
.
The corresponding in-buffer setting is: ‘#+STARTUP: lognoteclock-out’.