emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Dmitri Minaev" <minaev@gmail.com>
To: Deech <aditya_siram@hotmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Log Notes with Non-sequential states
Date: Tue, 16 Jan 2007 11:55:23 +0400	[thread overview]
Message-ID: <b6c377310701152355s3d6d3f84idfadcbb5624777fc@mail.gmail.com> (raw)
In-Reply-To: <loom.20070115T180854-772@post.gmane.org>

I like lognotestate so much that I use it even when it is not the
right thing to do :). BTW, I didn't have a chance yet to thank Carsten
for implementing it. It's great, thanks!

I'd say that it is quite comfortable to use it for oscillating between
states. You can also try to use tags to mark the pending tasks, but
lognotestate gives a way to timestamp such changes and log the
reasons. The only annoyance is that since the sequence has to be
linear and if the sequence is TODO-WAITING-DONE, you cannot jump from
TODO to DONE. In this case, I would simply change the sequence to
WAITING-TODO-DONE. After all, all tasks are WAITING to be started
before they go to the TODO state :).

On 1/15/07, Deech <aditya_siram@hotmail.com> wrote:
> Hi all,
> I am trying to use the lognotestate feature to log the progress of a project.
> However my projects go from WAITING to TODO and back to WAITING so there is no
> definate sequence.
>
> Is lognotestate even the right feature to use? Is there a better tool to log the
> actions taken in a project?
>
> Thanks...
> Deech
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>


-- 
With best regards,
Dmitri Minaev

      parent reply	other threads:[~2007-01-16  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 17:15 Log Notes with Non-sequential states Deech
2007-01-15 21:26 ` Carsten Dominik
2007-01-16 10:07   ` Dmitri Minaev
2007-01-16  7:55 ` Dmitri Minaev [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=b6c377310701152355s3d6d3f84idfadcbb5624777fc@mail.gmail.com \
    --to=minaev@gmail.com \
    --cc=aditya_siram@hotmail.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).