From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: resheduling from agenda buffer Date: Fri, 28 Sep 2007 18:03:13 +0200 Message-ID: <874pheeq0u.fsf@bzg.ath.cx> 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 1IbIJG-0001HG-2H for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 12:03:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IbIJE-0001E5-3x for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 12:03:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbIJD-0001Ds-UV for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 12:03:19 -0400 Received: from ug-out-1314.google.com ([66.249.92.172]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IbIJD-0003C1-B1 for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 12:03:19 -0400 Received: by ug-out-1314.google.com with SMTP id m4so1770281uge for ; Fri, 28 Sep 2007 09:03:17 -0700 (PDT) In-Reply-To: (Richard G. Riley's message of "Fri, 28 Sep 2007 17:30:24 +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: emacs-orgmode@gnu.org Richard G Riley writes: >> 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. Two issues here: (1) whether org-mode should give you visible hints for any change you make in the agenda buffer and (2) whether this change are to be automatically saved. For the first issue, this can be improved by displaying a timestamp when a new SCHEDULED: or DEADLINE: is added (just like the visible timestamp we have when pressing S-left/right on a headline: => <2007-09-28 ven>) For the second issue, I still think saving the modification should not be automated. It useful to see all the changes you made before saving them, and maybe you would agree with this once the first issue is fixed? -- Bastien