From: Ihor Radchenko <yantar92@posteo.net>
To: Tom Alexander <tom@fizz.buzz>
Cc: emacs-orgmode@gnu.org
Subject: [PATCH] Re: Description list with " :: " in the tag.
Date: Thu, 14 Sep 2023 11:25:10 +0000 [thread overview]
Message-ID: <87y1h9atex.fsf@localhost> (raw)
In-Reply-To: <3dfc2172-7521-4939-bc4c-a4959dd1af3a@app.fastmail.com>
"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>
prev parent reply other threads:[~2023-09-14 11:25 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
2023-09-20 9:00 ` Ihor Radchenko
2023-09-14 11:25 ` Ihor Radchenko [this message]
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=87y1h9atex.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=tom@fizz.buzz \
/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).