From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: resheduling from agenda buffer Date: Fri, 28 Sep 2007 17:19:26 +0200 Message-ID: <87r6kix1fl.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IbHcr-0004nx-BW for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:19:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IbHcq-0004nj-AB for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:19:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbHcq-0004ng-71 for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:19:32 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IbHcp-00029j-PF for emacs-orgmode@gnu.org; Fri, 28 Sep 2007 11:19:32 -0400 Received: by ug-out-1314.google.com with SMTP id m4so1761015uge for ; Fri, 28 Sep 2007 08:19:31 -0700 (PDT) In-Reply-To: (Richard G. Riley's message of "Fri, 28 Sep 2007 03:15:15 +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: > 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.) --=-=-= Content-Type: text/x-diff Content-Disposition: attachment; filename=org.el.patch diff -u /home/guerry/elisp/testing/org/org.el /home/guerry/elisp/testing/bzg/org.el --- /home/guerry/elisp/testing/org/org.el 2007-09-26 21:00:50.000000000 +0200 +++ /home/guerry/elisp/testing/bzg/org.el 2007-09-28 17:09:30.000000000 +0200 @@ -2199,7 +2199,7 @@ (defcustom org-agenda-skip-scheduled-if-done nil "Non-nil means don't show scheduled items in agenda when they are done. This is relevant for the daily/weekly agenda, not for the TODO list. And -it applied only to the actualy date of the scheduling. Warnings about +it applied only to the actually date of the scheduling. Warnings about an item with a past scheduling dates are always turned off when the item is DONE." :group 'org-agenda-skip @@ -2209,7 +2209,7 @@ "Non-nil means don't show deadines when the corresponding item is done. When nil, the deadline is still shown and should give you a happy feeling. This is relevant for the daily/weekly agenda. And it applied only to the -actualy date of the deadline. Warnings about approching and past-due +actually date of the deadline. Warnings about approching and past-due deadlines are always turned off when the item is DONE." :group 'org-agenda-skip :type 'boolean) @@ -13327,12 +13327,13 @@ ((eq what 'deadline) org-deadline-string) ((eq what 'closed) org-closed-string)) " ") - (org-insert-time-stamp - time - (or org-time-was-given - (and (eq what 'closed) org-log-done-with-time)) - (eq what 'closed) - nil nil (list org-end-time-was-given)) + (setq ts + (org-insert-time-stamp + time + (or org-time-was-given + (and (eq what 'closed) org-log-done-with-time)) + (eq what 'closed) + nil nil (list org-end-time-was-given))) (end-of-line 1)) (goto-char (point-min)) (widen) @@ -17133,7 +17134,7 @@ "Dispatch agenda commands to collect entries to the agenda buffer. Prompts for a character to select a command. Any prefix arg will be passed on to the selected command. The default selections are: -g + a Call `org-agenda-list' to display the agenda for current day or week. t Call `org-todo-list' to display the global todo list. T Call `org-todo-list' to display the global todo list, select only Diff finished. Fri Sep 28 17:09:42 2007 --=-=-= > 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... -- Bastien --=-=-= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --=-=-=--