From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is this proper time format?
Date: Fri, 09 Jun 2023 07:36:12 +0000 [thread overview]
Message-ID: <87h6rh140j.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB54550E0DB4C0D1DC2DB3AB01A250A@SJ0PR03MB5455.namprd03.prod.outlook.com>
David Masterson <dsmasterson@gmail.com> writes:
>> "Timestamp" is the general term we use. We make it explicit in the
>> parent section that timestamps may or may not have time specification:
>>
>> A timestamp is a specification of a date (possibly with a time) in a
>> special format, either =<2003-09-16 Tue>= or
>> =<2003-09-16 Tue 09:39>=
>
> Maybe I'm not explicit enough. In section 8.1 of the Org 9.6 manual is
> a subsection "Time/Date Range" that *implies* times are supported in
> ranges by the use of words "time" and "timestamp" when, above, you're
> saying they are undefined (unsupported?) for now. I'm merely saying
> adjust the manual to remove the implication.
Please check the manual from main branch of Org. It has more text:
- Time/Date range ::
#+cindex: timerange
#+cindex: date range
Two timestamps connected by =--= denote a range. In the agenda, the
headline is shown on the first and last day of the range, and on any
dates that are displayed and fall in the range. Here is an example:
#+begin_example
,** Meeting in Amsterdam
<2004-08-23 Mon>--<2004-08-26 Thu>
#+end_example
Timerange is a timestamp consisting of two time units connected by =-=
#+begin_example
,* Discussion on climate change
<2006-11-02 Thu 10:00-12:00>
#+end_example
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-06-09 7:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 16:58 Is this proper time format? David Masterson
2023-06-05 19:52 ` Ihor Radchenko
2023-06-05 21:03 ` David Masterson
2023-06-06 6:08 ` Ihor Radchenko
2023-06-06 18:01 ` David Masterson
2023-06-06 23:52 ` Samuel Wales
2023-06-07 5:40 ` David Masterson
2023-06-08 10:33 ` Ihor Radchenko
2023-06-08 23:09 ` David Masterson
2023-06-09 7:36 ` Ihor Radchenko [this message]
2023-06-10 2:34 ` David Masterson
2023-06-10 10:02 ` Ihor Radchenko
2023-06-11 0:01 ` David Masterson
2023-06-11 9:31 ` Ihor Radchenko
2023-06-12 0:19 ` David Masterson
2023-06-12 10:44 ` Ihor Radchenko
2023-06-11 6:20 ` David Masterson
2023-06-11 9:45 ` Ihor Radchenko
2023-06-12 0:16 ` David Masterson
2023-06-12 11:00 ` Ihor Radchenko
2023-06-12 18:02 ` David Masterson
2023-06-13 9:41 ` Ihor Radchenko
2023-06-14 6:16 ` David Masterson
2023-06-14 11:01 ` Ihor Radchenko
2023-06-15 3:35 ` David Masterson
2023-06-15 11:07 ` Ihor Radchenko
2023-06-15 16:04 ` David Masterson
2023-06-16 9:38 ` Ihor Radchenko
2023-06-17 0:54 ` David Masterson
2023-06-17 12:33 ` Ihor Radchenko
2023-06-18 3:57 ` David Masterson
2023-06-18 10:42 ` Ihor Radchenko
2023-06-18 19:05 ` David Masterson
2023-06-18 20:53 ` Ihor Radchenko
2023-06-19 18:13 ` David Masterson
2023-06-10 2:40 ` David Masterson
2023-06-23 12:18 ` Ihor Radchenko
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=87h6rh140j.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).