From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: Bernt Hansen <bernt@norang.ca>, emacs-orgmode@gnu.org
Subject: Re: Journal versus clock tables: Opposing requirements?
Date: Tue, 8 Nov 2011 09:23:19 +0100 [thread overview]
Message-ID: <68F95387-0EDF-4848-BFD1-E7DF045BABDA@gmail.com> (raw)
In-Reply-To: <CAMg28OuqeYzzPucTARS+5gYn8yw8wt6CzwAvZAO3NvhCRuw6sQ@mail.gmail.com>
On Nov 8, 2011, at 9:06 AM, Tommy Kelly wrote:
>> ... it depends on how often you require this weekly report...
>
> Ermm, weekly :-)
>
>> It should be possible to write code that walks your agenda, visits the
>> tasks, and copies and pastes the details to a temporary org buffer/file
>> just for your chronological report.
>
> Absolutely. But as I've been thinking about this, I'm realizing that
> in fact a key input requirement (as opposed to my two output
> requirements -- chronology plus clock tables) is ease of entry. As I
> begin some new chunk of work, I don't want to have to hunt around for
> the most appropriate heading to clock into and begin writing notes
> under. As a result, what's happening is two things. First, I'm just
> falling back on your single "Organization" catch-all task; second, I'm
> not writing *any* notes.
>
> With a chronological journal, there's no decision to be made. You just
> start logging at the end (or start) of the journal. But maybe
> something in the org-capture area is what I need. I've tried it before
> and didn't get very far, but I'll have another look.
Yes, capture you notes into a date tree and turn on the clock whenever
you start a new entry!
- Carsten
next prev parent reply other threads:[~2011-11-08 8:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 8:31 Journal versus clock tables: Opposing requirements? Tommy Kelly
2011-11-07 11:27 ` Bernt Hansen
2011-11-07 14:55 ` Tommy Kelly
2011-11-08 3:21 ` Bernt Hansen
2011-11-08 8:06 ` Tommy Kelly
2011-11-08 8:23 ` Carsten Dominik [this message]
2011-11-08 12:28 ` Bernt Hansen
2011-11-08 17:07 ` Bernt Hansen
2011-11-07 11:38 ` Olaf Dietsche
2011-11-07 14:51 ` Tommy Kelly
2011-11-07 17:19 ` Tommy Kelly
2011-11-08 9:04 ` Olaf Dietsche
2011-11-08 9:54 ` Carsten Dominik
2011-11-08 9:55 ` Tommy Kelly
2011-11-08 10:00 ` Carsten Dominik
2011-11-08 10:05 ` Sebastien Vauban
2011-11-08 10:15 ` Carsten Dominik
2011-11-08 10:33 ` Sebastien Vauban
2011-11-08 10:41 ` Tommy Kelly
2011-11-24 14:57 ` Eric S Fraga
2011-11-24 22:01 ` Olaf Dietsche
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=68F95387-0EDF-4848-BFD1-E7DF045BABDA@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.com \
/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).