From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is this proper time format?
Date: Fri, 09 Jun 2023 19:40:24 -0700 [thread overview]
Message-ID: <DS7PR03MB54476844F1748BAF948B201AA256A@DS7PR03MB5447.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87h6rh140j.fsf@localhost> (Ihor Radchenko's message of "Fri, 09 Jun 2023 07:36:12 +0000")
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Ihor Radchenko <yantar92@posteo.net> writes:
> 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:
Shouldn't have inlined the attachment -- here it is as an attachment.
Again, this is a patch to the main branch of Org on Savannah.
[-- Attachment #2: Patch to Org-Guide and Org-Manual --]
[-- Type: text/plain, Size: 6007 bytes --]
diff --git a/doc/org-guide.org b/doc/org-guide.org
index 95828e4c0..167f62e49 100644
--- a/doc/org-guide.org
+++ b/doc/org-guide.org
@@ -1088,12 +1088,12 @@ time information is called a /timestamp/ in Org mode.
:DESCRIPTION: Assigning a time to a tree entry.
:END:
-A timestamp is a specification of a date---possibly with a time or
-a range of times---in a special format, either =<2003-09-16 Tue>= or
-=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=.
-A timestamp can appear anywhere in the headline or body of an Org tree
-entry. Its presence causes entries to be shown on specific dates in
-the agenda (see [[*The Weekly/Daily Agenda]]). We distinguish:
+A timestamp is a specification of a date---possibly with a time or a
+range of times---in a special format, either =<2003-09-16 Tue>= or
+=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=. One or
+more timestamps can appear anywhere in the headline or body of an Org
+tree entry. Its presence causes entries to be shown on specific dates
+in the agenda (see [[*The Weekly/Daily Agenda]]). We distinguish:
- Plain timestamp; Event; Appointment ::
@@ -1132,15 +1132,25 @@ the agenda (see [[*The Weekly/Daily Agenda]]). We distinguish:
<%%(diary-float t 4 2)>
#+end_example
-- Time/Date range ::
+- Date range ::
- Two timestamps connected by =--= denote a range.
+ Two timestamps connected by =--= denote a date range. NOTE: time is
+ not specified in these timestamps -- just dates,
#+begin_example
,** Meeting in Amsterdam
<2004-08-23 Mon>--<2004-08-26 Thu>
#+end_example
+- Time range ::
+
+ Two times in a timestamp connected by =-= denote a time range.
+
+ #+begin_example
+ ,** Planning meeting
+ <2004-08-23 Mon 9:00-10:00>
+ #+end_example
+
- Inactive timestamp ::
Just like a plain timestamp, but with square brackets instead of
diff --git a/doc/org-manual.org b/doc/org-manual.org
index c11694849..824a46eaf 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -5991,42 +5991,32 @@ is used in a much wider sense.
:PROPERTIES:
:DESCRIPTION: Assigning a time to a tree entry.
:END:
-#+cindex: timestamps
-#+cindex: ranges, time
-#+cindex: date stamps
-#+cindex: deadlines
-#+cindex: scheduling
-
-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>=[fn:19]. A timestamp can appear anywhere in
-the headline or body of an Org tree entry. Its presence causes
-entries to be shown on specific dates in the agenda (see [[*Weekly/daily
-agenda]]). We distinguish:
+
+A timestamp is a specification of a date---possibly with a time or a
+range of times---in a special format, either =<2003-09-16 Tue>= or
+=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=. One or
+more timestamps can appear anywhere in the headline or body of an Org
+tree entry. Its presence causes entries to be shown on specific dates
+in the agenda (see [[*The Weekly/Daily Agenda]]). We distinguish:
- Plain timestamp; Event; Appointment ::
- #+cindex: timestamp
- #+cindex: appointment
A simple timestamp just assigns a date/time to an item. This is
just like writing down an appointment or event in a paper agenda.
- In the agenda display, the headline of an entry associated with
- a plain timestamp is shown exactly on that date.
#+begin_example
,* Meet Peter at the movies
<2006-11-01 Wed 19:15>
,* Discussion on climate change
- <2006-11-02 Thu>
+ <2006-11-02 Thu 20:00-22:00>
#+end_example
- Timestamp with repeater interval ::
- #+cindex: timestamp, with repeater interval
A timestamp may contain a /repeater interval/, indicating that it
applies not only on the given date, but again and again after
- a certain interval of N hours (h), days (d), weeks (w), months (m),
- or years (y). The following shows up in the agenda every Wednesday:
+ a certain interval of N days (d), weeks (w), months (m), or years
+ (y). The following shows up in the agenda every Wednesday:
#+begin_example
,* Pick up Sam at school
@@ -6037,46 +6027,36 @@ agenda]]). We distinguish:
#+cindex: diary style timestamps
#+cindex: sexp timestamps
- # Mentioned inside the footnote.
- #+findex: org-date
- #+findex: org-anniversary
- #+findex: org-cyclic
- #+findex: org-block
-
For more complex date specifications, Org mode supports using the
- special expression diary entries implemented in the
- [[info:emacs#Special Diary Entries][Emacs Calendar package]][fn:20].
- For example, with optional time:
+ special expression diary entries implemented in the Emacs Calendar
+ package. For example, with optional time:
#+begin_example
,* 22:00-23:00 The nerd meeting on every 2nd Thursday of the month
<%%(diary-float t 4 2)>
#+end_example
-- Time/Date range ::
+- 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:
+ Two timestamps connected by =--= denote a date range. NOTE: time is
+ not specified in these timestamps -- just dates,
#+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 =-=
+- Time range ::
+
+ Two times in a timestamp connected by =-= denote a time range.
#+begin_example
- ,* Discussion on climate change
- <2006-11-02 Thu 10:00-12:00>
+ ,** Planning meeting
+ <2004-08-23 Mon 9:00-10:00>
#+end_example
- Inactive timestamp ::
- #+cindex: timestamp, inactive
- #+cindex: inactive timestamp
Just like a plain timestamp, but with square brackets instead of
angular ones. These timestamps are inactive in the sense that they
do /not/ trigger an entry to show up in the agenda.
[-- Attachment #3: Type: text/plain, Size: 21 bytes --]
--
David Masterson
next prev parent reply other threads:[~2023-06-10 2:41 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
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 [this message]
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=DS7PR03MB54476844F1748BAF948B201AA256A@DS7PR03MB5447.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).