emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: akater <nuclearspace@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: One inconsistency with org-element parsers
Date: Thu, 16 Apr 2020 10:00:37 +0200	[thread overview]
Message-ID: <875zdz272y.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ftd4yvml.fsf@gmail.com> (akater's message of "Thu, 16 Apr 2020 03:09:22 +0000")


akater <nuclearspace@gmail.com> 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.


Nicolas Goaziou

      reply	other threads:[~2020-04-16  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  3:09 One inconsistency with org-element parsers akater
2020-04-16  8:00 ` Nicolas Goaziou [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:

  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=875zdz272y.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=nuclearspace@gmail.com \


* 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


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).