From: "Tom Alexander" <tom@fizz.buzz>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: Description list with " :: " in the tag.
Date: Tue, 19 Sep 2023 20:09:34 -0400 [thread overview]
Message-ID: <4bbd732f-5d1e-40a0-8f2a-b7778a617b42@app.fastmail.com> (raw)
In-Reply-To: <87zg1patgh.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Sorry for the delay, I've been busy in the IRLs. I've updated the patch to reflect that the parser grabs the text before the last " :: " and then parses it as objects. The new patch is attached.
--
Tom Alexander
On Thu, Sep 14, 2023, at 7:24 AM, Ihor Radchenko wrote:
> "Tom Alexander" <tom@fizz.buzz> writes:
>
>> I've written a patch (attached) with my proposed wording changes to
>> the documentation, should I be starting another thread or does
>> dropping it here work best?
>
> You can just modify subject with [PATCH], as I did.
>
>> ... I do not have commit access so I'd need
>> someone with such authority to do the last bit.
>
> Sure.
>
>> + =TAG-TEXT= is one of more objects from the standard set so long as
>> + they do not contain a newline character, until the last occurrence
>> + of the substring =" :: "= (two colons surrounded by whitespace,
>> + without the quotes).
>
> It does not fully represent what is going on - Org parser is top-down
> and does not parse objects before it is done parsing the descriptive
> list item. So,
>
> - *foo :: bar* does not actually contain bold markup
>
> Rather it is "* foo" tag + "bar* does not actually contain bold markup"
> description.
>
> What happens is that the parser splits the first line of the item by the
> last " :: " and only then proceeds with parsing the tag and description
> using standard set of objects:
>
> - <....> :: <text not containing :: >
>
> --
> 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>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-syntax.org-Fix-definition-of-description-list-ta.patch --]
[-- Type: text/x-patch; name="0001-org-syntax.org-Fix-definition-of-description-list-ta.patch", Size: 1353 bytes --]
From c8812bf7d81dc824d8ecf2c03368f58884773ddf Mon Sep 17 00:00:00 2001
From: Tom Alexander <tom@fizz.buzz>
Date: Wed, 13 Sep 2023 18:19:05 -0400
Subject: [PATCH] org-syntax.org: Fix definition of description list tags.
Description lists support objects in their tags and they support the substring " :: ".
---
org-syntax.org | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/org-syntax.org b/org-syntax.org
index 123fc232..fc5e9a37 100644
--- a/org-syntax.org
+++ b/org-syntax.org
@@ -470,9 +470,10 @@ BULLET COUNTER-SET CHECK-BOX TAG CONTENTS
+ CHECK-BOX (optional) :: A single whitespace character, an =X=
character, or a hyphen enclosed by square brackets (i.e. =[ ]=, =[X]=, or =[-]=).
+ TAG (optional) :: An instance of the pattern =TAG-TEXT ::= where
- =TAG-TEXT= represents a string consisting of non-newline characters
- that does not contain the substring =" :: "= (two colons surrounded by
- whitespace, without the quotes).
+ =TAG-TEXT= is the text up until the last occurrence of of the
+ substring =" :: "= (two colons surrounded by whitespace, without the
+ quotes) on that line. =TAG-TEXT= is then parsed with the standard
+ set of objects.
+ CONTENTS (optional) :: A collection of zero or more elements, ending
at the first instance of one of the following:
- The next item.
--
2.42.0
next prev parent reply other threads:[~2023-09-20 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:25 Description list with " :: " in the tag Tom Alexander
2023-09-09 3:15 ` Max Nikulin
2023-09-09 9:06 ` Ihor Radchenko
2023-09-10 4:22 ` Max Nikulin
2023-09-11 16:05 ` Tom Alexander
2023-09-13 22:52 ` Tom Alexander
2023-09-14 11:24 ` [PATCH] " Ihor Radchenko
2023-09-20 0:09 ` Tom Alexander [this message]
2023-09-20 9:00 ` Ihor Radchenko
2023-09-14 11:25 ` 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=4bbd732f-5d1e-40a0-8f2a-b7778a617b42@app.fastmail.com \
--to=tom@fizz.buzz \
--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).