From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>,
Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Extending the Org syntax by a custom exporter - how to do it?
Date: Sun, 16 Mar 2014 12:05:22 -0400 [thread overview]
Message-ID: <87bnx6ceub.fsf@gmail.com> (raw)
In-Reply-To: <87zjkqqrsy.fsf@gmail.com>
Hi Marcin and Nicolas,
2014ko martxoak 16an, Nicolas Goaziou-ek idatzi zuen:
>
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
>> I thought about it. But, as I said, I'm going to have two backends,
>> one for LaTeX, one for HTML. WOuld it be possible to have e.g.
>>
>> #+ATTR_TEST
>>
>> working for both?
>
> Of course. You decide, at the backend level, what attributes are read.
> For example, "ox-beamer.el" reads both "ATTR_LATEX" and "ATTR_BEAMER",
> when it makes sense.
>
>> (Anyway, options after #+BEGIN_MYBLOCK would be a bit nicer, since the
>> user would not have to type /that/ much.)
>
> This is backend specific data. It would not be nice to hide that fact.
I haven’t followed the thread closely, but it sounds like Marcin may be
considering both LaTeX and HTML output, which makes this not exactly
specific to a single backend.
>
> Options on the same line as the block opening string should be reserved
> for backend agnostic data. There is none for special blocks at the
> moment.
There is indeed no support for options on the #+begin_foo line. But
special blocks, and indeed any other element, can take a #+header: line.
It can fulfill the same functions as an #+attr_foo: line, but is seen by
all backends.
HTH,
--
Aaron Ecay
next prev parent reply other threads:[~2014-03-16 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 10:10 Extending the Org syntax by a custom exporter - how to do it? Marcin Borkowski
2014-03-15 11:10 ` John Kitchin
2014-03-15 11:25 ` Marcin Borkowski
2014-03-15 11:29 ` Marcin Borkowski
2014-03-15 21:22 ` Marcin Borkowski
2014-03-16 10:16 ` Nicolas Goaziou
2014-03-16 11:18 ` Marcin Borkowski
2014-03-16 11:57 ` Nicolas Goaziou
2014-03-16 13:33 ` Marcin Borkowski
2014-03-16 14:12 ` Nicolas Goaziou
2014-03-17 15:43 ` Marcin Borkowski
2014-03-16 16:05 ` Aaron Ecay [this message]
2014-03-17 16:31 ` Marcin Borkowski
2014-03-22 11:23 ` Nicolas Goaziou
2014-11-25 21:25 ` Marcin Borkowski
2014-11-25 21:46 ` Marcin Borkowski
2014-11-26 2:46 ` John Kitchin
2014-11-26 14:23 ` John Kitchin
2014-11-26 11:59 ` 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:
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=87bnx6ceub.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
--cc=n.goaziou@gmail.com \
/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).