From mboxrd@z Thu Jan 1 00:00:00 1970 From: PT Subject: org-read-date-prefer-future 'time doesn't always prefer future Date: Thu, 10 Dec 2009 16:15:07 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NIlgC-0006PL-2O for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 11:15:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NIlg7-0006Gn-GZ for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 11:15:47 -0500 Received: from [199.232.76.173] (port=47932 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NIlg7-0006GZ-6i for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 11:15:43 -0500 Received: from lo.gmane.org ([80.91.229.12]:36868) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NIlg7-00072j-DU for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 11:15:43 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NIlg3-0008VA-OI for emacs-orgmode@gnu.org; Thu, 10 Dec 2009 17:15:39 +0100 Received: from 94-21-242-200.pool.digikabel.hu ([94.21.242.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Dec 2009 17:15:39 +0100 Received: from spamfilteraccount by 94-21-242-200.pool.digikabel.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Dec 2009 17:15:39 +0100 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 This is a very useful setting, because it allows the user to quickly schedule a task into the future by simply entering the time, but it doesn't always do the right thing. Suppose I scheduled a task to 1pm, but I didn't have time to deal with it during the day. It's 5pm now. If I want to reschedule the task to tomorrow 10am then I can write simply 10am to the time prompt and it puts the task correctly to tomorrow 10am. However, if I want to reschedule it to tomorrow 2pm then I can't write simply 2pm, because then it schedules the task at 2pm today (which is past already, since it's 5 pm). The problem is the feature uses the task's own scheduled time to determine if a time is in the past, instead of the current time. It's Org-mode version 6.33