emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Wanrong Lin <wanrong.lin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New variable request: org-archive-todo-only
Date: Tue, 11 Dec 2007 15:35:22 +0100	[thread overview]
Message-ID: <878x41fget.fsf@bzg.ath.cx> (raw)
In-Reply-To: <475D9253.6040707@gmail.com> (Wanrong Lin's message of "Mon, 10 Dec 2007 14:24:03 -0500")

Wanrong Lin <wanrong.lin@gmail.com> writes:

> In my org file I have a mix of "actionable" items (TODO items) and
> informative items (notes, references and etc). Normally I only archive
> TODO items when they are done, and don't archive informative items
> (since most of them have some long-term value). So, can we add a new
> variable to "org-archive-todo-only" to control the behavior of following
> functions:
>
> 1. org-archive-subtree
> 2. org-archive-all-done

Good idea!

Maybe this could be more general like this:

(setq org-archive-maybe '((plain . never)
                          (todo  . confirm)
                          (done  . always)))

where "plain" refers to informative entries (no TODO keyword), "todo"
refers to entries with a TODO keyword, "done" refers to entries with 
a done-state TODO keyword.

This would apply for both org-archive-subtree and org-archive-all-done.

Maybe we could refine it a bit and have:

#+SEQ_TODO:   TODO(t) WAITING(w@) SOMEDAY(s$) | DONE(d) CANCELED(c@)
                                           ^

where the "$" sign means: always archive this todo keyword without
asking (i.e. override the value or `org-archive-maybe')

-- 
Bastien

  reply	other threads:[~2007-12-11 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 19:24 New variable request: org-archive-todo-only Wanrong Lin
2007-12-11 14:35 ` Bastien [this message]
2007-12-12  4:30   ` Wanrong Lin

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=878x41fget.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=wanrong.lin@gmail.com \
    /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).