From: ihor <ihor@antonovs.family>
To: emacs-orgmode@gnu.org
Subject: Re: org-element discovered inconsistensies
Date: Sat, 8 Jun 2019 19:18:24 -0400 [thread overview]
Message-ID: <18bd667a-6c5d-5870-1449-259714680560@antonovs.family> (raw)
In-Reply-To: <87muirznxx.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
Great! Thanks,
I think you missed Node Properties - they are still located under
Elements on Syntax page
https://orgmode.org/worg/dev/org-syntax.html#Elements
https://orgmode.org/worg/dev/org-syntax.html#Node_Properties
I think it should be moved to Greater Elements section
And it is also listed as Element on API page
https://orgmode.org/worg/dev/org-element-api.htm
I have also discovered more:
Syntax page states:
> With the exception of inlinetasks
<https://orgmode.org/worg/dev/org-syntax.html#Inlinetasks>, items
<https://orgmode.org/worg/dev/org-syntax.html#Plain_Lists_and_Items>,
planning
<https://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning>,
clocks
<https://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning>,
node properties
<https://orgmode.org/worg/dev/org-syntax.html#Node_Properties> and table
rows <https://orgmode.org/worg/dev/org-syntax.html#Table_Rows>, every
other element type can be assigned attributes.
But this list is not full - if you check the source code
https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-element.el#L3866
;; Item. +
;; Table Row. +
;; Node Property. +
;; Headline.
;; Sections (must be checked after headline).
;; Planning.+
;; Property drawer.
;; Paragraph.
;; Clock. +
;; Inlinetask. +
;; From there, elements can have affiliated keywords.
So Pragraph, Property Drawer, Sections and Headlines are missing from
this list
On 6/8/19 6:56 PM, Nicolas Goaziou wrote:
> Hello,
>
> ihor <ihor@antonovs.family> writes:
>
>> So these are things that I have discovered so far:
> [...]
>
> I think I fixed the issues you pointed out. Thank you.
>
> Regards,
>
[-- Attachment #2: Type: text/html, Size: 3506 bytes --]
next prev parent reply other threads:[~2019-06-08 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKJNb8-mKR9kOTVHv6vA654GaVaA6HJUksCkrT+C4-V_D=GtNQ@mail.gmail.com>
[not found] ` <CAKJNb8-8cdcQYFBLNgcrA=USh2LfvFYrdBOnfA+Cej4DU1BCaw@mail.gmail.com>
[not found] ` <CAKJNb88Rfz06jbM_BwRGpcufikzEoHuuG+xanK0q2KCEsp1juw@mail.gmail.com>
[not found] ` <87ef4l599r.fsf@nicolasgoaziou.fr>
2019-05-29 23:06 ` Fwd: Questions about org-element Ngor
2019-05-30 3:43 ` Nick Dokos
2019-06-04 3:12 ` org-element discovered inconsistensies ihor
2019-06-08 22:56 ` Nicolas Goaziou
2019-06-08 23:18 ` ihor [this message]
2019-06-10 9:15 ` 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=18bd667a-6c5d-5870-1449-259714680560@antonovs.family \
--to=ihor@antonovs.family \
--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).