From: Bernt Hansen <bernt@norang.ca>
To: Xavier Maillard <xma@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Day workflow: need your opinion
Date: Mon, 10 Aug 2009 17:36:00 -0400 [thread overview]
Message-ID: <87ljlrjqrj.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87k51be5d1.wl%xma@gnu.org> (Xavier Maillard's message of "Mon\, 10 Aug 2009 23\:17\:14 +0200")
Xavier Maillard <xma@gnu.org> writes:
> Thanks a lot Bernt. This is how I am doing things right now which
> "partially" works for me.
>
> I need a way to tag a TODO as INTERRUPTED automatically when
> clocking-in a new item through remember.
>
> Eg:
>
> Working on task A which is marked as STARTED. Someone calls me
> asking for help. I C-M-r a new clocked item, automatically
> marking previous clocked-in item (task A) as INTERRUPTED.
There is a variable for changing task states when clocking out a task.
Every task that clocks out but isn't finished is essentially
interrupted.
The variable org-clock-out-switch-to-state controls that IIRC but I've
never actually tried that (yet). I just leave my tasks in a STARTED
state. Anything for me that is STARTED is interrupted (partially worked
on and unfinished). My STARTED list tends to be less than 20 tasks
total (13 right now). I just use my STARTED agenda view to pick up the
in-progress tasks easily and clock one in.
>
> Even better would be to have something that could clock-out
> automatically when a task hits some tags: WAITING or INTERRUPTED.
>
> Do you know if it is possible ?
There is a org-after-todo-state-change-hook which you could probably use
to accomplish this.
>
> Also, while at it: how do you access a "daily report" of what has
> been done and how long it took to do ?
I look at my clock report data in the agenda. Just pull up a day or
week view and hit R for the report. You can insert clock reports in
your org files and this is the way I used to do this... but when agenda
reporting came along I abandoned that altogether.
HTH,
Bernt
prev parent reply other threads:[~2009-08-10 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 5:57 Day workflow: need your opinion Xavier Maillard
2009-08-04 9:39 ` Vedang
2009-08-10 21:10 ` Xavier Maillard
2009-08-04 9:46 ` Leo
2009-08-10 21:11 ` Xavier Maillard
2009-08-04 11:14 ` Benjamin Andresen
2009-08-04 14:53 ` Jonathan Arkell
2009-08-04 16:34 ` Bernt Hansen
2009-08-10 21:17 ` Xavier Maillard
2009-08-10 21:36 ` Bernt Hansen [this message]
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=87ljlrjqrj.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=xma@gnu.org \
/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).