From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wanrong Lin Subject: Re: Re: Active timestamp with notification in advance Date: Wed, 27 Feb 2008 21:20:10 -0500 Message-ID: <47C61A5A.40909@gmail.com> References: <47C48C56.6050206@gmail.com> <1F133D29-7823-413B-92D3-2B1844D8F507@science.uva.nl> <47C582C3.4090405@gmail.com> <873arexu8b.fsf@gollum.intra.norang.ca> <871w6x7tsz.fsf@bzg.ath.cx> <47C616FC.3030009@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUYNi-0002WY-2O for emacs-orgmode@gnu.org; Wed, 27 Feb 2008 21:20:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUYNg-0002V3-MZ for emacs-orgmode@gnu.org; Wed, 27 Feb 2008 21:20:21 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUYNg-0002Uz-Dv for emacs-orgmode@gnu.org; Wed, 27 Feb 2008 21:20:20 -0500 Received: from an-out-0708.google.com ([209.85.132.241]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JUYNg-00010H-8I for emacs-orgmode@gnu.org; Wed, 27 Feb 2008 21:20:20 -0500 Received: by an-out-0708.google.com with SMTP id c25so622473ana.84 for ; Wed, 27 Feb 2008 18:20:19 -0800 (PST) In-Reply-To: <47C616FC.3030009@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Wanrong Lin wrote: > >> > Thanks a lot for the suggestions, but manual workaround does not work > for me, as I want org to take care of giving me a notification in > advance in the agenda buffer. > > For SCHEDULED and plain active time stamp, I don't think we need to > have a default ahead notification setting as with deadlines, but it > would really be nice to support the <..... -3d> format. It would be > even nicer to have a new keyword (like "SCHEDULED@") that indicates a > strictly scheduled item (just a fancy term for "appointment") and > hence a default ahead notification setting can be applied. The lack of > real appointment support in org-mode in fact is a little bit puzzling > to me, since SCHEDULED item may or may not be strictly scheduled, > while plain time stamp item may or may not be something that needs to > take actions on (as it could be just an event). > > Wanrong > > Actually, I was wrong on the "lack of real appointment" support claim above. We can define a TODO heading with a *plain* active time stamp as an appointment, and hence maybe a default ahead notification can be applied to those items.