summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarsten Dominik <carsten.dominik@gmail.com>2012-10-15 08:38:54 +0200
committerCarsten Dominik <carsten.dominik@gmail.com>2012-10-15 08:38:54 +0200
commit6fae77a8d6c33199eb66666f51e507ba981622a8 (patch)
tree46fb36f74ace6a39afb4b090bf63b56033e94955
parent23aa91025973f1bd351f90adab4f85cdaecaaa6c (diff)
downloadorg-mode-6fae77a8d6c33199eb66666f51e507ba981622a8.tar.gz
Fix date prompt documentation
* doc/org.texi: Explain that date/time information at read-date prompt should start at the beginning, not anywhere in the middle of a long string.
-rw-r--r--doc/org.texi7
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/org.texi b/doc/org.texi
index c8f0afb..a6509af 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -5630,10 +5630,9 @@ the following column).
@vindex org-read-date-prefer-future
When Org mode prompts for a date/time, the default is shown in default
date/time format, and the prompt therefore seems to ask for a specific
-format. But it will in fact accept any string containing some date and/or
-time information, and it is really smart about interpreting your input. You
-can, for example, use @kbd{C-y} to paste a (possibly multi-line) string
-copied from an email message. Org mode will find whatever information is in
+format. But it will in fact accept date/time information in a variety of
+formats. Generally, the information should start at the beginning of the
+string. Org mode will find whatever information is in
there and derive anything you have not specified from the @emph{default date
and time}. The default is usually the current date and time, but when
modifying an existing timestamp, or when entering the second stamp of a