From: Eric S Fraga <esflists@gmail.com>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature request: simplify usage of special blocks (for beamer)
Date: Sun, 02 Dec 2018 11:58:03 +0000 [thread overview]
Message-ID: <87woosw378.fsf@gmail.com> (raw)
In-Reply-To: <CAELgYhe6=nM-PUg9mCXic=BJxW-O2Td1vOTtRbxukFAhSM5Bwg@mail.gmail.com> (Carlos Pita's message of "Sat, 1 Dec 2018 16:23:12 -0300")
On Saturday, 1 Dec 2018 at 16:23, Carlos Pita wrote:
> The idea is that stuff that is very specific to a backend X would be
> in :attrs_X, but stuff that is related to what makes the block
> semantically special could be in :args.
And this is where the challenge lies! The whole point of special blocks is that org knows nothing of their semantics. They are a "black box" and it would be difficult to identify export specific elements and general elements on this basis.
> Nevertheless special blocks will probably be backend specific in most
> cases.
Many but not all. And hence the difficulty.
Sorry for being negative. I sympathize fully with your aims as I use special blocks all the time and don't particularly like the attr lines either. But I see no general solution to this.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442
next prev parent reply other threads:[~2018-12-02 11:58 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 [this message]
2018-12-02 14:50 ` Carlos Pita
2018-12-02 15:30 ` Carlos Pita
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=87woosw378.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=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
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).