From: Carsten Dominik <firstname.lastname@example.org>
To: Jota Pin <email@example.com>
Cc: Peter Jones <firstname.lastname@example.org>, email@example.com
Subject: Re: Re: [Bulk] Re: clocksum and archived trees
Date: Sat, 21 Mar 2009 18:21:26 +0100 [thread overview]
Message-ID: <0A3ABDDA-0F8B-44F3-9BC7-5EE8A7D6B12A@uva.nl> (raw)
On Mar 20, 2009, at 3:59 AM, Jota Pin wrote:
> Le jeudi 19 mars 2009, Peter Jones a écrit :
>> Jota Pin <firstname.lastname@example.org> writes:
>>> I tried to figure out how to avoid having archived subtrees to
>>> to the sum of times showed with "Display Times" c-c c-x c-d.
>> I've been wondering something along the same lines myself. When
>> switching to column view via C-c C-x C-c it can sometimes take a long
>> time because of archive items.
Hi Peter, this case makes sense, for speed, and I have added
a variable org-columns-skip-archived-trees, with default t.
>> I haven't gotten around to looking into this yet. Maybe I'll try
>> to fix
>> this tomorrow when I get some time.
> Thanks, this would be great.
> Maybe an explanation of the reason to doing so is helpful:
> I like to see the time spent per subtree, but at the same time I do
> want to
> keep the archives in their original location: I use sometimes
> archives tags
> to store versions of the same subtree, and of course the clocks must
> no count
> twice there...
for this case I am not sure. The purpose or archiving is to mark a tree
as finished, but clearly any clocking times from this tree should still
contribute. I see that you are using ARCHIVE to mark a second version
of a given tree. If you need multiple versions, why don't you keep
older versions in another file or so?
Are there more opinions about this? Maybe I am seeing it wrong.....
> Same question for clock tables.
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
prev parent reply other threads:[~2009-03-21 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 20:12 clocksum and archived trees Jota Pin
2009-03-19 21:03 ` Peter Jones
2009-03-20 2:59 ` [Bulk] " Jota Pin
2009-03-21 17:21 ` Carsten Dominik [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).