From: John Hendy <jw.hendy@gmail.com>
To: "Filippo A. Salustri" <salustri@ryerson.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: another (possibly) noob question
Date: Tue, 15 Mar 2011 09:54:35 -0500 [thread overview]
Message-ID: <AANLkTikO42oCP5i8nuAnXzkyBTHJNGLz66pnaMvCydu4@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikPbYFNNYnM_-CzuftcZWr4xkkGhtp6UEqd0P6u@mail.gmail.com>
On Mon, Mar 14, 2011 at 11:15 PM, Filippo A. Salustri
<salustri@ryerson.ca> wrote:
> So,
> I've set org-provide-todo-statistics to t
> and org-hierarchical-todo-statistics to nil.
> I use a TODO sequence to identify projects. That is,
> (setq org-todo-keywords
> '((sequence "REVIEW(r)" "TODO(t)" "ACTIVE(a!)" "WAIT(w@)" "SOMEDAY(s)"
> "|"
> "DONE(d)" "CANCELED(c@)")
> (sequence "OPEN(O@!)" "WIP(W!)" "PAUSED(P@!)" "|" "CLOSED(C@!)")
> (sequence "PROJECT(p)" "|" "COMPLETED(x)")
> ))
> I then set level 1 headlines to be PROJECT and put [/] at the end of the
> headline.
> The hope is to see projects at a glance and get the fraction done too.
> All is as it should be, but for one thing.
> When I toggle or insert within a subtree, the headline for that project
> changes from PROJECT to ACTIVE if less than all tasks are done, and DONE if
> all tasks are done.
> Obviously, I want it to stay PROJECT.
> I've spent over an hour trying to figure this one out and I can't.
> Anyone got any advice?
I don't use this, but replicating your example, I don't get the behavior you do.
- I added your todo definitions to my .emacs
- I created a simple top-level headline in a blank file and used C-c
C-t to make it a PROJECT
- I added three second-level headlines and made them all TODOs
- I marked them done one by one and the top level always stayed as a PROJECT
My end result:
,-----
| * PROJECT some project [3/3]
| ** DONE do something
| CLOSED: [2011-03-15 Tue 09:51]
| ** DONE do something else
| CLOSED: [2011-03-15 Tue 09:50]
| ** DONE do something further
| CLOSED: [2011-03-15 Tue 09:49]
`-----
Perhaps list your org-mode version? Others will be able to debug
better than I can. Perhaps start with a simple, blank file as well (or
maybe you already are?). I can't figure out what would trigger it from
PROJECT to the keyword in another sequence without directly specifying
such.
Good luck,
John
> Cheers.
> Fil
>
> --
> Filippo A. Salustri, Ph.D., P.Eng.
> Mechanical and Industrial Engineering
> Ryerson University
> 350 Victoria St, Toronto, ON
> M5B 2K3, Canada
> Tel: 416/979-5000 ext 7749
> Fax: 416/979-5265
> Email: salustri@ryerson.ca
> http://deseng.ryerson.ca/~fil/
>
next prev parent reply other threads:[~2011-03-15 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 4:15 another (possibly) noob question Filippo A. Salustri
2011-03-15 14:54 ` John Hendy [this message]
2011-03-15 17:20 ` Filippo A. Salustri
2011-03-15 17:29 ` Manish
[not found] ` <AANLkTikL1QM+Mi9dtAutvYGizff5Pj0sfwkTXyCCqAEM@mail.gmail.com>
2011-03-15 21:55 ` Filippo A. Salustri
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=AANLkTikO42oCP5i8nuAnXzkyBTHJNGLz66pnaMvCydu4@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=salustri@ryerson.ca \
/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).