From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Tom Gillespie <tgbugs@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>,
Timothy <tecosaur@gmail.com>
Subject: Re: Some commentary on the Org Syntax document
Date: Sat, 04 Dec 2021 15:43:36 +0100 [thread overview]
Message-ID: <87wnkksa5j.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87y250eah0.fsf@localhost> (Ihor Radchenko's message of "Sat, 04 Dec 2021 22:00:27 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
>> There are actually three types of elements: not all elements can contain
>> objects.
>
> You are right. However, I am not sure if it is a good idea to mention
> this in the introduction part of the syntax document.
>
> Maybe we can just say "... lesser elements" that cannot contain other
> elements."? Then, we mention that some elements cannot contain objects
> in the description of those elements.
But then, you do not remove the ambiguity that is condemned in this
thread. The greater element/element and greater element/lesser element
distinctions are equivalent, albeit not identical.
IIUC, you want three terms for elements (I am not even talking about
secondary strings, which can hold objects that are not part of
contents), and probably two for objects: terminal and non-terminal.
Regards,
next prev parent reply other threads:[~2021-12-04 14:44 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnkksa5j.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
--cc=tgbugs@gmail.com \
--cc=yantar92@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.