From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: relative scheduling Date: Tue, 09 Oct 2007 22:01:26 +0100 Message-ID: <87sl4kdmu1.fsf@bzg.ath.cx> References: <3jve9n6oxf.fsf@home.net> <29178d4ffee1d1d7a249c67ca0592b65@science.uva.nl> <20071009133340.46b19f75@dhcp-296-6> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IfLGo-0005Rs-SL for emacs-orgmode@gnu.org; Tue, 09 Oct 2007 16:01:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IfLGl-0005QQ-Bw for emacs-orgmode@gnu.org; Tue, 09 Oct 2007 16:01:34 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IfLGl-0005QN-65 for emacs-orgmode@gnu.org; Tue, 09 Oct 2007 16:01:31 -0400 Received: from fk-out-0910.google.com ([209.85.128.189]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IfLGk-0002p9-LI for emacs-orgmode@gnu.org; Tue, 09 Oct 2007 16:01:30 -0400 Received: by fk-out-0910.google.com with SMTP id 19so1649623fkr for ; Tue, 09 Oct 2007 13:01:29 -0700 (PDT) In-Reply-To: <20071009133340.46b19f75@dhcp-296-6> (John Rakestraw's message of "Tue, 9 Oct 2007 13:33:40 -0400") 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 John Rakestraw writes: > Perhaps this is personal preference, but somehow it seems more > reasonable to me to reschedule from today. This not only avoids > problems if (I don't know that) an event is already scheduled, but it > also fits in better with my thinking about tasks. Even if it's Monday > and I'm thinking about rescheduling a task that's now scheduled for > Wednesday, I'm still inclined to think about the new date relative to > today rather than relative to Wednesday. > > So, even if it's merely my personal preference, that's my vote ;). Since we're voting, I hope I'll cause no damage to any further agreement by voting for the *other* solution :) Most of the time, I'm rescheduling when: 1. the date of the event moved; in this case, it easier to reschedule relatively to the initial date. 2. the date is *today* and I want to delay the task: in this case, there is no difference between the two solution :) Okay, you might ponder my vote like this: (* vote .75) -- Bastien