From: Ihor Radchenko <yantar92@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: Tom Gillespie <tgbugs@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Some commentary on the Org Syntax document
Date: Sat, 04 Dec 2021 15:40:21 +0800 [thread overview]
Message-ID: <874k7og6my.fsf@localhost> (raw)
In-Reply-To: <87y250oo3o.fsf@gmail.com>
Timothy <tecosaur@gmail.com> writes:
> ⁃ Elements
> • Greater Elements
> • (other) Elements
>
> to
>
> ⁃ Elements
> • Greater Elements
> • Lesser Elements
This sounds reasonable. We can change
- Three categories are used to classify these environments: “Greater
elements”, “elements”, and “objects”, from the broadest scope to the
narrowest. The word “element” is used for both Greater and non-Greater
elements, the context should make that clear.
+ Two main categories are used to classify these environments:
"elements" and "objects", from the broadest scope to the narrowest.
"Elements" consist of "greater elements" that can contain other
elements and objects and "lesser elements" that can only contain
objects.
>> [Comments on headings and sections]
>
> This accords with my reading of the document and the way I’ve implemented things
> in OrgMode.jl (see <https://github.com/tecosaur/OrgMode.jl/blob/main/src/types/sections.jl>).
One small clarification. The headline structure is actually
(headline (optional whitespace) (optional section) (optional repeat nester-headlines))
Section may not start immediately after the first newline but also after
you skip blank chars in front.
For example:
* This is a headline _without_ section, even though it contains some newlines
* Another headline
Section starts at the word "section" and spans all the way to the next headline or EOB
* Next headline
Best,
Ihor
next prev parent reply other threads:[~2021-12-04 7:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 9:23 Some commentary on the Org Syntax document Timothy
2021-12-02 19:00 ` Tom Gillespie
2021-12-02 19:16 ` Timothy
2021-12-04 5:26 ` Tom Gillespie
2021-12-04 6:17 ` Ihor Radchenko
2021-12-04 6:48 ` Timothy
2021-12-04 7:40 ` Ihor Radchenko [this message]
2021-12-04 8:09 ` Timothy
2021-12-04 9:41 ` Nicolas Goaziou
2021-12-04 14:00 ` Ihor Radchenko
2021-12-04 14:43 ` Nicolas Goaziou
2021-12-05 6:30 ` Ihor Radchenko
2021-12-05 9:28 ` Nicolas Goaziou
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=874k7og6my.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
--cc=tgbugs@gmail.com \
/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).