emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Richard G Riley <rileyrgdev@googlemail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: resheduling from agenda buffer
Date: Fri, 28 Sep 2007 16:07:47 +0200	[thread overview]
Message-ID: <c8648e0a8fe662d2e83d8170ca36668e@science.uva.nl> (raw)
In-Reply-To: <pvbqbnk2u4.fsf@dev.shamrockirishbar.com>

On Sep 28, 2007, at 3:15, Richard G Riley wrote:

> Two questions:
> 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?

his is just a bug, fixed now for the next version.

> 2) What is the reason behind having to manually "refresh" after a
> reschedule in the agenda buffer, why does it not do it automatically?

Initially the reason was technical.  Constructing the agenda can take
a second or more, to automatically reconstructing it after each change
forbids itself.  Just moving around a changed line can be difficult.

However, after giving up on trying to change everything live, I now
happen to think that this is in fact good.   What you really do is look
at a list of tasks and appointments, and you do want to push things
around.  I really like to be able to modify several lines before
getting a rearranged display.  For example:

- When things move around with each change I make, I constantly
   have to follow the changes with my eyes and memory, this is more

- I change a TODO entry to DONE.  That means it should not even be
   in the agenda anymore, and a live update would just get rid of
   the item.  If you made a mistake in marking it done, it is hard to
   find the entry back and change it back.

- I want to reschedule an item to next week.  Will the display then move
   to next week? So I need to go back to today to continue working?

Things like this.  You *do* get visual feedback that an entry has been
modified, and "r" is not hard to press.
So even if I knew how to change it, I would not want to do it.

> (ps Carsten, if you are reading this I found the issue with
> org-return-follows-link - it has to be set before loading Org so cant 
> be
> used in normal customization block).

Yes, the docstring of that variable says so.

- Carsten

  reply	other threads:[~2007-09-29  8:49 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 [this message]
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
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=c8648e0a8fe662d2e83d8170ca36668e@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrgdev@googlemail.com \


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