emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Dan Griswold <dgriswol@rochester.rr.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: confused about logging
Date: Mon, 12 Apr 2010 20:55:39 -0400	[thread overview]
Message-ID: <87mxx8p3w4.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87wrwc2owz.fsf@cantor.home> (Dan Griswold's message of "Mon\, 12 Apr 2010 20\:10\:04 -0400")

Dan Griswold <dgriswol@rochester.rr.com> 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

-Bernt

  reply	other threads:[~2010-04-13  0:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  0:10 confused about logging Dan Griswold
2010-04-13  0:55 ` Bernt Hansen [this message]
2010-04-13  2:22   ` Nick Dokos
2010-04-13  2:28     ` Bernt Hansen
2010-04-13  5:40     ` Carsten Dominik
2010-04-13 11:53       ` Bernt Hansen
2010-04-14 11:49 ` Carsten Dominik
2010-04-17 16:53   ` Dan Griswold

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=87mxx8p3w4.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=dgriswol@rochester.rr.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).