[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] Re: date marking with (org-diary)

From: Ulf Stegemann
Subject: [Orgmode] Re: date marking with (org-diary)
Date: Mon, 08 Sep 2008 17:06:42 +0200
User-agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.21 (linux)

Hi Carsten, all,

Carsten Dominik <address@hidden> wrote:

> On Aug 15, 2008, at 10:45 AM, Ulf Stegemann wrote:


>> Including agenda items into the diary with '&%%(org-diary ...' is
>> something I personally find pretty useless as the dates of those items
>> are not fontified in the calendar. Using '%%(org-diary ...' would be
>> fine but the entries to use (':scheduled', ':todo' aso) cannot be
>> limited any further. This not only leads to unacceptable delays while
>> calendar tries to fontify its buffer but also to a calendar with nearly
>> everyday marked. My intent was to mark dates with appointments only (I
>> have scheduled items, todos etc. nearly everyday so there's no need to
>> mark them). In my case this means that (org-diary) would need to
>> distinct between different TODO keywords. However, filtering based on
>> tags or date/time formats would be fine, too.
>> My question now is: Is there currently any way to achieve such a
>> filtering with (org-diary)? And if not, are there any plans to enhance
>> (org-diary) in that direction?


> this is not supported yet, and I have no concrete plans to implement
> this.  Marking entries in the calendar will always be unacceptably
> slow, because the way the calendar/diary implements this is creating
> the list of appointment for each of the 90+ days in the calendar
> display.  Even with filtering, this would be slow - basically one
> would have to rewrite the code in the diary.

okay, then I guess we have to live with it.


>            Making use of the cursor position in the agenda
>            ===============================================


> * Picking a date for scheduling/deadline in the agenda

Thank you for pointing this out. It's not quite what I was looking for
but nevertheless it's a good workaround. Thanks for your help.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]