From: Torben Hoffmann <torben.lehoff@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Archiving logged work time
Date: Wed, 19 Dec 2012 09:57:38 +0100 [thread overview]
Message-ID: <CABf3pCnEpS9CMCWLdbPepwNmjGgsnARKt=cWmkS0xk5zN8UBZQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
Hi,
I have been using org-mode for 6 months to track my working time, but now I
am stepping my usage up a bit since I have found it useful to have all my
to-dos in one tool.
Until now I have had a template file with the things I work on, so that I
can easily create a new file every week. This is drive by a need to report
time every week to a fixed set of activities.
So far I have just moved the old file and then created a new file with all
my tasks in.
However, now that I am using more of org-mode I am not so sure that
this monolithic time tracking file is a good idea, but I am not sure about
how I can archive just the logged time entries, but keep the activity for
logging time on next week.
When I stand on a line with a CLOCK entry the archive function will archive
the whole sub-tree that I am standing in.
It might be that I should just create a number of files for the major
things I am working on and then archive the task as well as the time logged
against it every week. This means that I would have to retype the task for
the next week, but if that is the best way of doing it I will start doing
that.
Advice most welcome - I am in learning mode and want to improve my usage of
org-mode.
Cheers,
__
/orben
--
http://www.linkedin.com/in/torbenhoffmann
[-- Attachment #2: Type: text/html, Size: 1653 bytes --]
next reply other threads:[~2012-12-19 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 8:57 Torben Hoffmann [this message]
2012-12-24 0:32 ` Archiving logged work time Bastien
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='CABf3pCnEpS9CMCWLdbPepwNmjGgsnARKt=cWmkS0xk5zN8UBZQ@mail.gmail.com' \
--to=torben.lehoff@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).