From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pete Ley <peteley11235@gmail.com>
Subject: Re: Entering Repeating Scheduled Tasks in the Minibuffer
Date: Wed, 10 Dec 2014 14:29:21 -0800
Message-ID: <87iohj3zr2.fsf@enterprise.sectorq.net>
References: <87388nils7.fsf@be.cs.appstate.edu>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44457)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peteley11235@gmail.com>) id 1XyplI-0000fw-Ar
	for emacs-orgmode@gnu.org; Wed, 10 Dec 2014 17:29:45 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peteley11235@gmail.com>) id 1Xypl9-0006Uy-AB
	for emacs-orgmode@gnu.org; Wed, 10 Dec 2014 17:29:36 -0500
Received: from mail-pa0-x22f.google.com ([2607:f8b0:400e:c03::22f]:61642)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peteley11235@gmail.com>) id 1Xypl9-0006Up-3Y
	for emacs-orgmode@gnu.org; Wed, 10 Dec 2014 17:29:27 -0500
Received: by mail-pa0-f47.google.com with SMTP id kq14so3675362pab.34
	for <emacs-orgmode@gnu.org>; Wed, 10 Dec 2014 14:29:25 -0800 (PST)
In-Reply-To: <87388nils7.fsf@be.cs.appstate.edu> (Kenneth Jacker's message of
	"Wed, 10 Dec 2014 10:09:44 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: khj@cs.appstate.edu
Cc: emacs-orgmode@gnu.org

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

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.