emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: hymie! <hymie@lactose.homelinux.net>
To: emacs-orgmode@gnu.org
Subject: tasks, clocks, and notes
Date: Thu, 12 Feb 2015 16:06:53 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150212T164133-180@post.gmane.org> (raw)

Greetings.

I have a funny feeling I asked this before, but I can't remember and I
couldn't find it in a search.

So let's say I have a task -- fix a computer.  I add some memory, I test the
new memory and that doesn't solve the problem, and then I finally figure out
it was the video driver.

I could log that this way:

* fix the computer
**  added memory to the machine
    CLOCK: [2015-01-28 Wed 12:36] -- [2015-01-28 Wed 13:14]
**  memory didn't resolve the problem
    CLOCK: [2015-01-28 Wed 13:28] -- [2015-01-28 Wed 13:53]
**  finally found it -- it was the video driver
    CLOCK: [2015-01-29 Thu 09:12] -- [2015-01-29 The 11:30]

but then my Agenda will have pretty disjoint notes about "added memory to
the machine".  I'd prefer that the Agenda either say "fix the computer"
or (even better) "fix the computer -- added memory to the machine".

Is there something I can do that would add "notes" to an individual clock
entry, something like

* fix the computer
    CLOCK: [2015-01-28 Wed 12:36] -- [2015-01-28 Wed 13:14]
    added memory to the machine
    CLOCK: [2015-01-28 Wed 13:28] -- [2015-01-28 Wed 13:53]
    memory didn't resolve the problem
    CLOCK: [2015-01-29 Thu 09:12] -- [2015-01-29 The 11:30]
    finally found it -- it was the video driver

that would still leave the clock lines "attached" to the main task, but
still keep some individual notes about the various pieces of the task?

--hymie!

             reply	other threads:[~2015-02-12 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 16:06 hymie! [this message]
2015-02-12 17:29 ` tasks, clocks, and notes Subhan Michael Tindall
2015-02-13 14:07   ` hymie

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=loom.20150212T164133-180@post.gmane.org \
    --to=hymie@lactose.homelinux.net \
    --cc=emacs-orgmode@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).