Re: One inconsistency with org-element parsers

[Nicolas Goaziou]

Hello,

akater <address@hidden> writes:

> I want to make it easier for users to define custom non-inline blocks
> (and operations on them). So I studied parsers in =org-element.el= and
> stumbled upon the following seeming inconsistency:
>
> Plists for =comment-block=, =example-block=, =export-block=, =src-block=
> all have neither ~:contents-begin~ nor ~:contents-end~ in them, while
> plists for =center-block=, =quote-block=, =verse-block= have both.

:contents-begin and :contents-end means there is something to parse
in-between. It doesn't make sense for the block types in the first
category, where the contents are not meant to be Org syntax.

Regards,

-- 
Nicolas Goaziou