From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard G Riley Subject: Re: resheduling from agenda buffer Date: Fri, 28 Sep 2007 17:30:24 +0200 Message-ID: References: <87r6kix1fl.fsf@bzg.ath.cx> 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 1IbHnX-0008CU-45 for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:30:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IbHnV-0008Bo-1p for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:30:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbHnU-0008Bl-Ux for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:30:32 -0400 Received: from ug-out-1314.google.com ([66.249.92.175]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IbHnU-0004Xw-Hb for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:30:32 -0400 Received: by ug-out-1314.google.com with SMTP id m4so1763353uge for ; Fri, 28 Sep 2007 08:30:30 -0700 (PDT) In-Reply-To: <87r6kix1fl.fsf@bzg.ath.cx> (Bastien's message of "Fri\, 28 Sep 2007 17\:19\:26 +0200") 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: Bastien Cc: emacs-orgmode@gnu.org Bastien writes: > Richard G Riley writes: > >> 1) When following the instruction from the following link and >> rescheduling from the agenda buffer, why do I always get >> >> "Item scheduled for nil" in the message bufffer? > > I think this is a bug. > > Try this patch (also fixing small typos.) > > > >> 2) What is the reason behind having to manually "refresh" after a >> reschedule in the agenda buffer, why does it not do it automatically? > > I think the reason is to warn you about the modification without having > to save it. Actually reschedule often happens more than once before you > need to save the modified buffers, so it makes sense to only save when > you're done with all the modification... It doesn't really make sense because as you reschedule its easy to forget which ones you already have rescheduled and end up trying to reschedule an already rescheduled one. Which is exactly what happened to me. Like other operations on the agenda it's my (noob) opinion that it should refresh immediately or only confusion (as in this case) results.