From: Carsten Dominik <carsten.dominik@gmail.com>
To: PT <spamfilteraccount@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Option to prefer future for times too
Date: Thu, 1 Oct 2009 13:11:07 +0200 [thread overview]
Message-ID: <EB5F3C07-2749-4859-BD2F-9CDF6036A504@gmail.com> (raw)
In-Reply-To: <loom.20091001T101448-471@post.gmane.org>
On Oct 1, 2009, at 10:21 AM, PT wrote:
> Currently, I'm using Google Calendar and it's quick add syntax is very
> convenient:
>
> http://www.google.com/support/calendar/bin/answer.py?hl=en&answer=36604#text
>
>
> Of course, Org has similar capabilites, but I found one thing which
> google
> calendar does better: if it's 4pm and I add an event for 8am then GCal
> schedules it for 8am tomorrow.
>
> Org, on the the other hand, schedules it for 8am today even if that
> time
> is already passed.
>
> I never add past events and I think it's quite atypical. Shouldn't
> be an
> option similar to org-read-date-prefer-future for times
> too, so that timestamps also prefer the future when no date given?
Hi PT (what does that stand for???)
I did not implement this case on purpose, because this can be quite
confusing if the time for tomorrow is near the time now.
Changing the time by a few minutes can make the resulting
date skip to tomorrow. But I guess it is OK as an option:
(setq org-read-date-prefer-future 'time)
should now create the behavior you were asking for.
- Carsten
prev parent reply other threads:[~2009-10-01 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 8:21 Option to prefer future for times too PT
2009-10-01 11:11 ` Carsten Dominik [this message]
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=EB5F3C07-2749-4859-BD2F-9CDF6036A504@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=spamfilteraccount@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).