From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: org-expiry.el v0.2
Date: Mon, 07 Jan 2008 08:21:01 +0000 [thread overview]
Message-ID: <87bq7ygi6q.fsf@bzg.ath.cx> (raw)
Hi folks,
good morning! Here is org-expiry.el, a first attempt to implement an
expiry mechanism. Your last real chance to get rid of all those tasks
on your org files.
http://www.cognition.ens.fr/~guerry/u/org-expiry.el
This is pretty preliminary, but maybe already useful.
Enjoy!
========================================================================
Here is what the Comment section says:
By default, entries that have no EXPIRY property are considered to be
new (i.e. 0 day old) and only entries older than one year go to the
expiry process, which consist in adding the ARCHIVE tag. None of your
tasks will be deleted with the default settings. When does an entry
expires?
Consider this entry:
* Stop watching TV
:PROPERTIES:
:CREATED: <2008-01-07 lun 08:01>
:EXPIRY: <2008-01-09 08:01>
:END:
This entry will expire on the 9th, january 2008.
* Stop watching TV
:PROPERTIES:
:CREATED: <2008-01-07 lun 08:01>
:EXPIRY: +1w
:END:
This entry will expire on the 14th, january 2008, one week after its
creation date.
What happen when an entry is expired? Nothing until you explicitely M-x
org-expiry-process-entries When doing this, org-expiry will check for
expired entries and request permission to process them.
Processing an expired entries means calling the function associated with
`org-expiry-handler-function'; the default is to add the tag :ARCHIVE:,
but you can also add a EXPIRED keyword or even archive the subtree.
Is this useful? Well, when you're in a brainstorming session, it might
be useful to know about the creation date of an entry, and be able to
archive those entries that are more than xxx days/weeks old.
When you're in such a session, you can insinuate org-expiry like this:
M-x org-expiry-insinuate
Then, each time you're pressing M-RET to insert an item, the CREATION
property will be automatically added. Same when you're scheduling or
deadlining items. You can deinsinuate: M-x org-expiry-deinsinuate
========================================================================
--
Bastien
reply other threads:[~2008-01-07 8:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bq7ygi6q.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.