From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Re: confused about logging Date: Tue, 13 Apr 2010 07:53:41 -0400 Message-ID: <87wrwbh8l6.fsf@gollum.intra.norang.ca> References: <87wrwc2owz.fsf@cantor.home> <87mxx8p3w4.fsf@gollum.intra.norang.ca> <10974.1271125339@gamaville.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O1egl-00037C-Sr for emacs-orgmode@gnu.org; Tue, 13 Apr 2010 07:53:55 -0400 Received: from [140.186.70.92] (port=39064 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O1egj-00034O-78 for emacs-orgmode@gnu.org; Tue, 13 Apr 2010 07:53:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O1egh-0004yb-Ej for emacs-orgmode@gnu.org; Tue, 13 Apr 2010 07:53:53 -0400 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:61707) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O1egh-0004yR-Ch for emacs-orgmode@gnu.org; Tue, 13 Apr 2010 07:53:51 -0400 In-Reply-To: (Carsten Dominik's message of "Tue\, 13 Apr 2010 07\:40\:40 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: Dan Griswold , nicholas.dokos@hp.com, emacs-orgmode@gnu.org Carsten Dominik writes: > On Apr 13, 2010, at 4:22 AM, Nick Dokos wrote: > >> Bernt Hansen wrote: >> >>> Dan Griswold writes: >>> >>>> Hi all, >>>> >>>> I have a repeating task, like so: >>>> >>>> *** TODO Print copies :@PRINT: >>>> SCHEDULED: <2010-03-09 Tue ++1w> >>>> >>>> I would like to have things set so that when I change the todo >>>> state, >>>> and the schedule advances, then there will not be any logging done. >>>> >>>> However, with org-log-repeat, org-log-done, and org-log-done-with- >>>> time >>>> all set to nil (indeed, it appears all org-log-X vars are set to >>>> nil), >>>> I get a timestamp in a property drawer when I advance the >>>> schedule, like >>>> so: >>>> >>>> *** TODO Print copies :@PRINT: >>>> SCHEDULED: <2010-04-13 Tue ++1w> >>>> :PROPERTIES: >>>> :LAST_REPEAT: [2010-04-12 Mon 20:06] >>>> :END: >>>> >>>> This happens with an emacs environment started with emacs -q, and >>>> a file >>>> that contains only the above entry. >>>> >>>> I don't need or want such information recorded. But I don't know >>>> how to >>>> stop it, and I don't know where else to look for the responsible >>>> variable. >>>> >>>> Any hints? >>> >>> Set the property >>> >>> :LOGGING: nil >>> >> >> I don't think that works - and I also don't think that there is a >> way to >> do what Dan wants, currently. The code in org.el:org-auto-repeat- >> maybe >> looks like this: >> >> .... >> (when repeat >> (if (eq org-log-repeat t) (setq org-log-repeat 'state)) >> (setq to-state (or (org-entry-get nil "REPEAT_TO_STATE") >> org-todo-repeat-to-state)) >> (unless (and to-state (member to-state org-todo-keywords-1)) >> (setq to-state (if (eq interpret 'type) last-state head))) >> (org-todo to-state) >> (org-entry-put nil "LAST_REPEAT" (format-time-string >> (org-time-stamp-format t t))) >> >> .... >> >> and the LAST_REPEAT property is set unconnditionally. At least, that's >> how I read it. > > > This is correct. Should we change this? LAST_REPEAT is used for the > clock display > of repeating tasks. It's not really useful if there is no clocking data for the task -- so maybe we can skip setting it when no clock data exists? -Bernt