From: Van L <van@scratch.space>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: time range, timestamps // was: docstring typoes in org-read-date-force-compatible-dates
Date: Fri, 4 Jan 2019 13:36:33 +1100 [thread overview]
Message-ID: <F3C88F4B-1469-4F73-8CAE-499046DBE8B6@scratch.space> (raw)
In-Reply-To: <878t01w5vz.fsf@kyleam.com>
> Kyle Meyer wrote:
>
> In the future, please send
> generated patches with git format-patch so that they include a commit
> message (see <https://orgmode.org/worg/org-contribute.html#org31412be>
> for instructions).
Thanks Kyle. Noted.
I am muddling my way through
[info:org#Creating timestamps]
[info:org#The date/time prompt]
and see that org-evaluate-time-range does nothing for
<2019-01-04 Fri 11:00-12:15>
which was created using the “11am+2:15” style from
— quote
You can specify a time range by giving start and end times or by
giving a start time and a duration (in HH:MM format). Use one or two
dash(es) as the separator in the former case and use ’+’ as the
separator in the latter case, e.g.:
11am-1:15pm ⇒ 11:00-13:15
11am--1:15pm ⇒ same as above
11am+2:15 ⇒ same as above
Parallel to the minibuffer prompt, a calendar is popped up(2). When
you exit the date prompt,
— quote ends
exporting that to ASCII in a buffer transforms the time range to
<2019-01-04 Fri 11:00>–<2019-01-04 Fri 12:15>
Now, that formatting put back in the Org buffer does work for org-evaluate-time-range, as follows:
<2019-01-04 Fri 12:34>-<2019-01-04 Fri 12:35> 00:01
;; Using the C-u C-c C-y
next prev parent reply other threads:[~2019-01-04 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 1:11 docstring typoes in org-read-date-force-compatible-dates Van L
2019-01-04 1:47 ` Kyle Meyer
2019-01-04 2:36 ` Van L [this message]
2019-01-05 17:43 ` time range, timestamps // was: " Kyle Meyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F3C88F4B-1469-4F73-8CAE-499046DBE8B6@scratch.space \
--to=van@scratch.space \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.