From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adam Spiers <orgmode@adamspiers.org>
Subject: Re: managing a work log
Date: Sat, 21 Sep 2013 23:08:59 +0100
Message-ID: <20130921220859.GC20610@pacific.linksys.moosehall>
References: <20130612173442.GN1063@pacific.linksys.moosehall>
	<87y59rp6j5.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49132)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <orgmode@adamspiers.org>) id 1VNVMW-0007QF-Uk
	for emacs-orgmode@gnu.org; Sat, 21 Sep 2013 18:09:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <orgmode@adamspiers.org>) id 1VNVMS-0004bW-2i
	for emacs-orgmode@gnu.org; Sat, 21 Sep 2013 18:09:12 -0400
Content-Disposition: inline
In-Reply-To: <87y59rp6j5.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@gnu.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>

Hi Bastien,

Sorry for the incredibly delayed response to this ...

On Sun, Jun 30, 2013 at 11:22:41PM +0200, Bastien wrote:
> Adam Spiers <orgmode@adamspiers.org> writes:
> > With `org-archive-mark-done' set to `t', entries will be marked as
> > done when `org-archive-subtree' is invoked.  However, this does not
> > honour the expected behaviour when `org-log-done' is set to `'time',
> > i.e. that a `CLOSED: [timestamp]' line will be inserted just after the
> > headline.  Is that a bug/feature, or am I missing something?
> 
> I get the same behavior but there is a ARCHIVE_TIME property,
> which tells you what time the entry was archived-and-marked-done.
> Why would you want redundant information with a CLOSED timestamp
> here?  Are you handling the CLOSED cookie in a specific way?

ARCHIVE_TIME is not honoured by log-mode.  I have a custom agenda
command which sets org-agenda-start-with-log-mode to '(closed clock)
and org-agenda-entry-types to '(:timestamp :sexp), so that I can
easily create a weekly work report to mail out to my team.  The CLOSED
cookie is required in order for DONE items to appear in this report.