From: Bastien <email@example.com>
Subject: Re: resheduling from agenda buffer
Date: Fri, 28 Sep 2007 17:19:26 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Richard G. Riley's message of "Fri, 28 Sep 2007 03:15:15 +0200")
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Richard G Riley <firstname.lastname@example.org> 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.)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: org.el.patch --]
[-- Type: text/x-diff, Size: 2299 bytes --]
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
@@ -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."
@@ -13327,12 +13327,13 @@
((eq what 'deadline) org-deadline-string)
((eq what 'closed) org-closed-string))
- (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
+ (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)))
@@ -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:
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
[-- Attachment #3: Type: text/plain, Size: 411 bytes --]
> 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...
[-- Attachment #4: Type: text/plain, Size: 204 bytes --]
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2007-09-28 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 1:15 resheduling from agenda buffer Richard G Riley
2007-09-28 14:07 ` Carsten Dominik
2007-09-29 12:45 ` Carsten Dominik
2007-09-28 15:19 ` Bastien [this message]
2007-09-28 15:30 ` Richard G Riley
2007-09-28 15:50 ` Egli Christian (KIRO 41)
2007-09-28 16:09 ` Bastien
2007-09-28 16:17 ` Richard G Riley
2007-09-28 16:10 ` Richard G Riley
2007-09-28 16:03 ` Bastien
2007-09-28 18:14 ` John Wiegley
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).