emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: resheduling from agenda buffer
Date: Fri, 28 Sep 2007 18:03:13 +0200	[thread overview]
Message-ID: <874pheeq0u.fsf@bzg.ath.cx> (raw)
In-Reply-To: <pak5qa4xkf.fsf@dev.shamrockirishbar.com> (Richard G. Riley's message of "Fri, 28 Sep 2007 17:30:24 +0200")

Richard G Riley <rileyrgdev@googlemail.com> 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?


  parent reply	other threads:[~2007-09-28 16:03 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
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 [this message]
2007-09-28 18:14     ` John Wiegley

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:

  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=874pheeq0u.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \


* 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).