From: Eric S Fraga <esflists@gmail.com>
To: ConcreteVitamin <concretevitamin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to generate clock report for hours worked each day?
Date: Mon, 25 Sep 2017 08:39:27 +0100 [thread overview]
Message-ID: <87fubb1b2o.fsf@t3610> (raw)
In-Reply-To: <CAG2+eog1xPb43ZWAUeWQwDXkt3YmXD46Jwk-k0kiZOk8zryDwg@mail.gmail.com> (ConcreteVitamin's message of "Mon, 25 Sep 2017 03:58:13 +0000")
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Monday, 25 Sep 2017 at 03:58, ConcreteVitamin wrote:
> Thanks! This workflow works.
>
> I can't help but wonder, does my use case show that in org-mode philosophy,
> tasks are best filed under a plain entry, not within a datetree?
I would say that the org-mode philosophy is what works for you is
perfect!
My own workflow is that I use a date tree for "short" tasks, those that
will be done usually well within a single day's activity. Longer tasks
are "projects" and they tend to have their own full structure. E.g. I
have main headlines for teaching, research, and admin and I clock into
those while my date tree will be things like "Meet with student X",
"submit proposal", "prepare agenda for meeting", etc.
But everybody does things differently and that is the best thing about
org: it doesn't impose any particular approach.
--
: Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-09-25 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 20:51 How to generate clock report for hours worked each day? ConcreteVitamin
2017-09-24 2:04 ` Matt Lundin
2017-09-24 5:28 ` ConcreteVitamin
2017-09-24 14:35 ` Matt Lundin
2017-09-25 3:58 ` ConcreteVitamin
2017-09-25 7:39 ` Eric S Fraga [this message]
2017-09-26 18:27 ` ConcreteVitamin
2017-09-27 5:57 ` Eric S Fraga
2017-09-28 23:43 ` ConcreteVitamin
2017-09-29 12:58 ` Eric S Fraga
2017-10-02 9:17 ` Yasushi SHOJI
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=87fubb1b2o.fsf@t3610 \
--to=esflists@gmail.com \
--cc=concretevitamin@gmail.com \
--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).