emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: akater <nuclearspace@gmail.com>
To: emacs-orgmode@gnu.org
Subject: One inconsistency with org-element parsers
Date: Thu, 16 Apr 2020 03:09:22 +0000	[thread overview]
Message-ID: <87ftd4yvml.fsf@gmail.com> (raw)

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.

Parameters ~contents-begin~ and ~contents-end~ are defined almost
everywhere (the only exception is, =src-block= parser never defines
~contents-begin~) but are not returned in plists by four parsers

Should something be done about this? I'm removing some boilerplate from
the parsers and could reuse existing parameters to put them into plists
but I don't understand the semantics yet so won't necessarily be able to
add ~:contents-begin~ to src-blocks. Maybe they are simply unnecessary
in these plists?

             reply	other threads:[~2020-04-16  3:18 UTC|newest]

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

  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=87ftd4yvml.fsf@gmail.com \
    --to=nuclearspace@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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