From: Richard G Riley <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: resheduling from agenda buffer
Date: Fri, 28 Sep 2007 17:30:24 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Bastien's message of "Fri\, 28 Sep 2007 17\:19\:26 +0200")
Bastien <firstname.lastname@example.org> writes:
> Richard G Riley <email@example.com> 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.
next prev parent reply other threads:[~2007-09-28 15:30 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
2007-09-28 15:30 ` Richard G Riley [this message]
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).