emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Carlos Pita <carlosjosepita@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: simplify usage of special blocks (for beamer)
Date: Sun, 2 Dec 2018 12:30:18 -0300	[thread overview]
Message-ID: <CAELgYhfXHsoCsXWehV2pKpFJsaNS21O_LZboAtfdL0FO+Cq3uQ@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhd4gM0OfxmvLWt8-Mv7=fj35ZEaVCFRmW+jMNtTP-zN0Q@mail.gmail.com>

I would also like to elaborate on another aspect of this.

#+ATTR_xxx serves two purposes:

a. As a syntactical means of attaching extra information to
syntactically constrained elements (as tables or images). For this
purpose the _xxx part is irrelevant, only the affiliation to an
element matters.

b. As a way of differentiating between different sets of attributes
and thus dispatching the appropriate set to the appropriate backend.

In the case of special blocks, which are syntactically capable of
directly taking arguments, just as SRC blocks do, (a) doesn't apply.
This brings about the possibility of a syntactic shortcut at the cost
of (b). So, a general rule could be:

i. A backend xxx interprets the argument to a special block as if it
were the argument to an affiliated ATTR_xxx.

ii. In case of conflict ATTR_xxx wins.

iii. It's well understood (and documented!) that, by doing so, ability
to export to other backends (point 2 above) may be compromised.

Thus the user would take advantage of this shortcut only when he/she
is already stuck with some particular output format. Also, for users
implementing kinda DSLs, having this special blocks with special
arguments is a handy feature.

Let's add this to my list of suggestions as proposal (4), again
related to but mostly independent of the other ones, although it's
expected that something like (2) would have to be implemented in order
to get (3) or (4).

Best regards
--
Carlos

next prev parent reply	other threads:[~2018-12-02 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 16:24 Feature request: simplify usage of special blocks (for beamer) Carlos Pita
2018-12-01 18:28 ` Eric S Fraga
2018-12-01 18:41   ` Carlos Pita
2018-12-01 19:23     ` Carlos Pita
2018-12-02 11:58       ` Eric S Fraga
2018-12-02 14:50         ` Carlos Pita
2018-12-02 15:30           ` Carlos Pita [this message]
2018-12-02 20:42       ` Nicolas Goaziou
2018-12-02 21:05         ` Carlos Pita
2018-12-02 11:55     ` Eric S Fraga

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=CAELgYhfXHsoCsXWehV2pKpFJsaNS21O_LZboAtfdL0FO+Cq3uQ@mail.gmail.com \
    --to=carlosjosepita@gmail.com \
    --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

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