emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard G Riley <rileyrgdev@googlemail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: resheduling from agenda buffer
Date: Fri, 28 Sep 2007 18:17:28 +0200	[thread overview]
Message-ID: <8dlkaqbw87.fsf@dev.shamrockirishbar.com> (raw)
In-Reply-To: <87zlz6db6b.fsf@bzg.ath.cx> (Bastien's message of "Fri\, 28 Sep 2007 18\:09\:16 +0200")

Bastien <bzg@altern.org> writes:

> "Egli Christian (KIRO 41)" <christian.egli@credit-suisse.com> writes:
>> I think the reason is the principle of least surprise. 
> Agreed. That's also why rescheduling should perhaps leave some
> persistent warning in the agenda buffer (as S-left/right does).
> I guess it would solve the issue Richard was concerned about.

Most 100% certainly. See the other reply. The S-<left,right>
functionality is spot on. As a noob I believe I am more likely to spot these
inconsistencies that established users. The other reply might have been
private so I include it below:

| While I can understand that, it certainly surprises the user to try and
| reschedule a task that isn't really there. I would suggest that the only
| sensible and usable and consistent thing to do is to mark it as changed
| like with the S-<left,right> .. in this case it hilites the entry as
| changed but you can continue to work on it. And then refresh (r)
| obviously moves all tasks to their correct positions while leaving the
| cursor at the current/next line.
| The functionality for S-<lft,right> is perfect.

  reply	other threads:[~2007-09-28 16:17 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 [this message]
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=8dlkaqbw87.fsf@dev.shamrockirishbar.com \
    --to=rileyrgdev@googlemail.com \
    --cc=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).