From: "Tom Alexander" <tom@fizz.buzz>
To: emacs-orgmode@gnu.org
Subject: [PATCH] Clarify that REST is not supported on the start TIME in a time-range timestamp.
Date: Mon, 02 Oct 2023 17:45:28 -0400 [thread overview]
Message-ID: <cad27389-f885-4da0-87f4-f68bfb42148e@app.fastmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
If REST is included in the first TIME on a time-range timestamp then the entire timestamp becomes a single range-less timestamp. To test I used the following test document:
```
[1970-01-01 Thu 8:15-13:15foo]
[1970-01-01 Thu 8:15foo-13:15]
```
The first line parses as a timerange from 8:15-13:15.
The second line parses as a single timestamp at 8:15.
--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-syntax.org-Timestamps-Clarify-that-REST-is-not-s.patch --]
[-- Type: text/x-patch; name="0001-org-syntax.org-Timestamps-Clarify-that-REST-is-not-s.patch", Size: 1616 bytes --]
From b1114e983d961d48e1d837b8d2ad209a976a5417 Mon Sep 17 00:00:00 2001
From: Tom Alexander <tom@fizz.buzz>
Date: Mon, 2 Oct 2023 17:35:28 -0400
Subject: [PATCH] * org-syntax.org (Timestamps): Clarify that REST is not
supported on the start TIME in a time-range timestamp.
If REST is included in the first TIME on a time-range timestamp then the entire timestamp becomes a single range-less timestamp. To test I used the following test document:
```
[1970-01-01 Thu 8:15-13:15foo]
[1970-01-01 Thu 8:15foo-13:15]
```
The first line parses as a timerange from 8:15-13:15.
The second line parses as a single timestamp at 8:15.
---
org-syntax.org | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/org-syntax.org b/org-syntax.org
index c2061431..0c326ba8 100644
--- a/org-syntax.org
+++ b/org-syntax.org
@@ -1686,9 +1686,10 @@ YYYY-MM-DD DAYNAME
- DAYNAME (optional) :: A string consisting of non-whitespace
characters except =+=, =-=, =]=, =>=, a digit, or =\n=.
+ TIME (optional) :: An instance of the pattern =H:MMREST= where =H=
- represents a one to two digit number (and can start with =0=), and =M=
- represents a single digit. =REST= can contain anything but =\n= or
- closing bracket.
+ represents a one to two digit number (and can start with =0=), and
+ =M= represents a single digit. =REST= can contain anything but =\n=
+ or closing bracket. =REST= cannot exist on the start TIME in a
+ time-range timestamp (the patterns with =TIME-TIME=).
+ REPEATER-OR-DELAY (optional) :: An instance of the following pattern:
#+begin_example
MARK VALUE UNIT
--
2.42.0
next reply other threads:[~2023-10-02 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 21:45 Tom Alexander [this message]
2023-10-02 23:43 ` [PATCH] Clarify that REST is not supported on the start TIME in a time-range timestamp Tom Alexander
2023-10-04 9:02 ` Ihor Radchenko
2023-10-07 1:20 ` Tom Alexander
2023-10-07 8:33 ` 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=cad27389-f885-4da0-87f4-f68bfb42148e@app.fastmail.com \
--to=tom@fizz.buzz \
--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).