From: Rainer Stengele <rainer.stengele@online.de>
To: John Wiegley <jwiegley@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: `f' in agenda view
Date: Thu, 13 Oct 2011 10:47:16 +0200 [thread overview]
Message-ID: <4E96A594.30102@online.de> (raw)
In-Reply-To: <m262k4lb92.fsf@gmail.com>
Am 04.10.2011 23:04, schrieb John Wiegley:
>>>>>> Dave Abrahams <dave@boostpro.com> writes:
>
>> It always strikes me as odd that `f' in agenda view moves the item forward
>> by a day even if that leaves it still in the past. Typically if I have an
>> overdue item, I just want to schedule it for today or a certain number of
>> days in the future, and as it stands it's even a bit non-obvious when I've
>> finally bumped it up to today if it's a few days old. Shouldn't the first
>> `f' on an overdue item schedule it for today?
>
> Just to clarify, by 'f' dave means `org-agenda-date-later'. I believe he's
> using my keybinding for this command...
>
>> I'm happy to hack something locally if the group doesn't agree, but moving
>> things around in the past seems like such a corner case that I thought maybe
>> this would be a better default behavior.
>
> I agree with Dave here. 'f' on a past-dated item maybe should move it today
> on the first press, and then into the future on subsequent presses.
>
> John
>
>
>
+1
Me too I sometimes run into this situation where I just want to shift past-dated items to today.
I never had a use case where I wanted to shift an item from "past" to "past+n-days<today".
Rainer
next prev parent reply other threads:[~2011-10-13 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 19:35 `f' in agenda view Dave Abrahams
2011-10-04 21:04 ` John Wiegley
2011-10-04 22:30 ` `org-agenda-date-later' (was: `f') " Dave Abrahams
2011-10-13 8:47 ` Rainer Stengele [this message]
2011-10-13 9:38 ` `f' " Rainer Stengele
2011-10-13 13:59 ` Dave Abrahams
2011-10-13 19:09 ` John Wiegley
2011-10-14 14:28 ` Rainer Stengele
2011-10-16 10:33 ` Carsten Dominik
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=4E96A594.30102@online.de \
--to=rainer.stengele@online.de \
--cc=emacs-orgmode@gnu.org \
--cc=jwiegley@gmail.com \
/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).