emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Benjamin Andresen <benny@in-ulm.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 6.32trans (release_6.32b.165.g3547); :LOGGING: property works differently from #+SEQ_TODO
Date: Fri, 13 Nov 2009 09:29:28 +0100	[thread overview]
Message-ID: <A06BEE8D-EB66-429E-8FF3-26221C4CB9BA@gmail.com> (raw)
In-Reply-To: <87r5s5qsj5.fsf@in-ulm.de>

Hi Benjamin,

a conflict is created because you are explicitly requesting to
record the state change to TODO as well.

Please replace

  :LOGGING:  TODO(!) | DONE(!)

with

  :LOGGING:  DONE(!)

HTH

- Carsten



On Nov 11, 2009, at 11:12 AM, Benjamin Andresen wrote:

> In a file that looks like this:
>
> #+SEQ_TODO: TODO(!) | DONE(!)
>
> * TODO Shave (Explicit logging)
>  SCHEDULED: <2009-11-13 Fri .+2d/4d>
>  - State "TODO"       from "DONE"       [2009-11-11 Wed 11:04]
>  :PROPERTIES:
>  :LOGGING:  TODO(!) | DONE(!)
>  :STYLE:    habit
>  :END:
>
> * TODO Shave (No explicit logging)
>  SCHEDULED: <2009-11-13 Fri .+2d/4d>
>  - State "DONE"       from "TODO"       [2009-11-11 Wed 11:04]
>  :PROPERTIES:
>  :STYLE:    habit
>  :END:
>
> ---
>
> The explicit logging reverses the logtime states.
> "TODO" from "DONE" vs. "DONE" from "TODO", even though it's configured
> in the same syntax.
>
> This is unexpected behaviour for org-habit and org-habit guilt-trips  
> me
> even though I'm perfectly shaven! :-)
>
>
> Emacs  : GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, X toolkit)
> of 2009-11-04 on stewie
> Package: Org-mode version 6.32trans (release_6.32b.165.g3547)
>
> current state:
> ==============
> (setq
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-export-preprocess-hook '(org-export-blocks-preprocess)
> org-tab-first-hook '(org-hide-block-toggle-maybe)
> org-src-mode-hook '(org-src-mode-configure-edit-buffer)
> org-confirm-shell-link-function 'yes-or-no-p
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide- 
> drawers
> 		  org-cycle-show-empty-lines org-optimize-window-after-visibility- 
> change)
> org-mode-hook '((lambda nil
> 		  (org-add-hook (quote change-major-mode-hook) (quote org-show- 
> block-all)
> 		   (quote append) (quote local))
> 		  )
> 		 )
> org-confirm-elisp-link-function 'yes-or-no-p
> org-occur-hook '(org-first-headline-recenter)
> )
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

      reply	other threads:[~2009-11-13  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 10:12 Org-mode version 6.32trans (release_6.32b.165.g3547); :LOGGING: property works differently from #+SEQ_TODO Benjamin Andresen
2009-11-13  8:29 ` Carsten Dominik [this message]

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=A06BEE8D-EB66-429E-8FF3-26221C4CB9BA@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=benny@in-ulm.de \
    --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).