From: Rainer Stengele <rainer.stengele@diplan.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: relative scheduling
Date: Tue, 09 Oct 2007 22:26:22 +0200 [thread overview]
Message-ID: <470BE3EE.4020200@diplan.de> (raw)
In-Reply-To: <87sl4kdmu1.fsf@bzg.ath.cx>
Bastien schrieb:
> John Rakestraw <lists@johnrakestraw.com> writes:
>
>> Perhaps this is personal preference, but somehow it seems more
>> reasonable to me to reschedule from today. This not only avoids
>> problems if (I don't know that) an event is already scheduled, but it
>> also fits in better with my thinking about tasks. Even if it's Monday
>> and I'm thinking about rescheduling a task that's now scheduled for
>> Wednesday, I'm still inclined to think about the new date relative to
>> today rather than relative to Wednesday.
>>
>> So, even if it's merely my personal preference, that's my vote ;).
>
> Since we're voting, I hope I'll cause no damage to any further agreement
> by voting for the *other* solution :)
>
> Most of the time, I'm rescheduling when:
>
> 1. the date of the event moved; in this case, it easier to reschedule
> relatively to the initial date.
>
> 2. the date is *today* and I want to delay the task: in this case, there
> is no difference between the two solution :)
>
> Okay, you might ponder my vote like this: (* vote .75)
>
I see passed events in agenda view and therefore see easily how may days
they are already "behind".
Hence I would personally (!) also find it more "intuitive" to reschedule
relatively.
rainer
next prev parent reply other threads:[~2007-10-09 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 12:32 relative scheduling Richard G Riley
2007-10-09 16:09 ` Carsten Dominik
2007-10-09 17:33 ` John Rakestraw
2007-10-09 21:01 ` Bastien
2007-10-09 20:26 ` Rainer Stengele [this message]
2007-10-09 20:32 ` John Wiegley
2007-10-09 21:56 ` Eddward DeVilla
2007-10-10 6:29 ` Bastien
2007-10-10 7:07 ` Carsten Dominik
2007-10-11 23:22 ` Richard G Riley
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470BE3EE.4020200@diplan.de \
--to=rainer.stengele@diplan.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).