From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: postponing todos
Date: Tue, 07 Aug 2007 02:56:23 +0200 [thread overview]
Message-ID: <87643s9n7s.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87tzrcfe16.fsf@bzg.ath.cx> (Bastien's message of "Tue\, 07 Aug 2007 01\:18\:13 +0200")
Bastien <bzg@altern.org> writes:
>> I would like to quickly (by using shortcuts) postpone a todo entry from
>> the agenda buffer by:
>> - 1-2-3 day
>> - coming monday/friday
>> - next monday/friday
>>
>> What is possible with current org mode?
>
> I don't think so, and i'm not sure on how it could be implemented.
>
> Maybe a :WarningAtDay: property? Conceptually this requires that we're
> able to distinguish between postponing the date a todo is displayed on
> and postponing the todo itself (the day it's supposed to be done)...
> All this might be a bit confusing.
Trying to think further, i stumbled on this idea: what about having
something like an _AGENDA suffix for properties that would make the
agenda decide whether it should get the entry or not?
For example, here is a todo:
,----
| * Try to avoid stupid examples
| :PROPERTIES:
| :WarningAtDay_AGENDA: <2007-11-11 dim>
| :END:
`----
When getting entries for the agenda display, Org might an entry with
such a _AGENDA property. Then Org's job would be to check whether this
entry has to be included in the results or not. For doing so, it will
have to call a user-defined function like :
,----
| (defun org-agenda-get-entry:WarningAtDay (param)
| ...
| [Returns t or nil depending on param]
| ...)
`----
If the function returns t (e.g. if the function above says that today is
later than the value of WarningAtDay_AGENDA), then the todo is included.
This way each user could (easily) define its own rules for deciding what
entries should appear in the agenda display.
But enough speculation for tonight :)
--
Bastien
next prev parent reply other threads:[~2007-08-07 0:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 15:42 postponing todos ignotus
2007-08-06 23:18 ` Bastien
2007-08-07 0:56 ` Bastien [this message]
2007-08-07 8:41 ` ignotus
2007-08-07 1:47 ` Eddward DeVilla
2007-08-07 8:25 ` ignotus
2007-08-07 17:13 ` Bastien
2007-08-07 20:03 ` Christian Egli
2007-08-07 20:14 ` Christian Egli
2007-08-09 5:05 ` Carsten Dominik
2007-08-11 14:29 ` ignotus
2007-08-21 10:19 ` Carsten Dominik
2007-08-21 10:43 ` Carsten Dominik
2007-08-21 11:33 ` Bastien
2007-08-11 15:31 ` ignotus
2007-08-11 16:34 ` Bastien
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=87643s9n7s.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 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).