From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Option to prefer future for times too Date: Thu, 1 Oct 2009 13:11:07 +0200 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtJZ7-0002ao-9W for emacs-orgmode@gnu.org; Thu, 01 Oct 2009 07:11:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtJZ2-0002Y8-By for emacs-orgmode@gnu.org; Thu, 01 Oct 2009 07:11:16 -0400 Received: from [199.232.76.173] (port=57749 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtJZ2-0002Y5-5C for emacs-orgmode@gnu.org; Thu, 01 Oct 2009 07:11:12 -0400 Received: from mail-ew0-f208.google.com ([209.85.219.208]:38460) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtJZ1-0004Wl-Qt for emacs-orgmode@gnu.org; Thu, 01 Oct 2009 07:11:11 -0400 Received: by ewy4 with SMTP id 4so29142ewy.31 for ; Thu, 01 Oct 2009 04:11:10 -0700 (PDT) In-Reply-To: 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: PT Cc: emacs-orgmode@gnu.org On Oct 1, 2009, at 10:21 AM, PT wrote: > Currently, I'm using Google Calendar and it's quick add syntax is very > convenient: > > http://www.google.com/support/calendar/bin/answer.py?hl=en&answer=36604#text > > > Of course, Org has similar capabilites, but I found one thing which > google > calendar does better: if it's 4pm and I add an event for 8am then GCal > schedules it for 8am tomorrow. > > Org, on the the other hand, schedules it for 8am today even if that > time > is already passed. > > I never add past events and I think it's quite atypical. Shouldn't > be an > option similar to org-read-date-prefer-future for times > too, so that timestamps also prefer the future when no date given? Hi PT (what does that stand for???) I did not implement this case on purpose, because this can be quite confusing if the time for tomorrow is near the time now. Changing the time by a few minutes can make the resulting date skip to tomorrow. But I guess it is OK as an option: (setq org-read-date-prefer-future 'time) should now create the behavior you were asking for. - Carsten