emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pete Ley <peteley11235@gmail.com>
To: khj@cs.appstate.edu
Cc: emacs-orgmode@gnu.org
Subject: Re: Entering Repeating Scheduled Tasks in the Minibuffer
Date: Wed, 10 Dec 2014 14:29:21 -0800	[thread overview]
Message-ID: <87iohj3zr2.fsf@enterprise.sectorq.net> (raw)
In-Reply-To: <87388nils7.fsf@be.cs.appstate.edu> (Kenneth Jacker's message of "Wed, 10 Dec 2014 10:09:44 -0500")

>PS  What is the meaning of "(=>F)" that appears at the end of the

I believe this means org has chosen the future option of an ambiguous
input. e.g., it is December 10th. I use C-c . to create a timestamp and
simply put in "9". The closest date that matches is December 9th, but
there is a setting (I think org-read-date-prefer-future) that makes it
prefer to choose a date in the future, so it is letting you know that it
is opting for the future date instead of the closest date.

I could be wrong, but that is my understanding.

  reply	other threads:[~2014-12-10 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 15:09 Entering Repeating Scheduled Tasks in the Minibuffer Kenneth Jacker
2014-12-10 22:29 ` Pete Ley [this message]
2014-12-16  1:46   ` Kenneth Jacker
     [not found] <D0B4FD4A.16A3B%jay.iyer@sandisk.com>
2015-01-02 22:22 ` Kenneth Jacker

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=87iohj3zr2.fsf@enterprise.sectorq.net \
    --to=peteley11235@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=khj@cs.appstate.edu \


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