emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* org-expiry.el v0.2
@ 2008-01-07  8:21 Bastien
  0 siblings, 0 replies; only message in thread
From: Bastien @ 2008-01-07  8:21 UTC (permalink / raw)
  To: emacs-orgmode

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-01-07  8:21 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-07  8:21 org-expiry.el v0.2 Bastien

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).