From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: 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:18:32 +0100 [thread overview]
Message-ID: <20140316121832.2bc543c1@aga-netbook> (raw)
In-Reply-To: <874n2ysb30.fsf@gmail.com>
Dnia 2014-03-16, o godz. 11:16:03
Nicolas Goaziou <n.goaziou@gmail.com> napisał(a):
> Hello,
>
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
> > OK, so I did some research, and I found out that "special blocks"
> > are probably the best idea. So, items with checkboxes
> > whose :parent is a special block like "MCT" or "SCT" could behave
> > accordingly. Still, I can't see in the docs any mentions about
> > possible properties of special blocks. Is it possible to make an
> > exporter so that I could say
> >
> > #+BEGIN_ANSWER :lines 2
> > This is an answer.
> > #+END_ANSWER
> >
> > so that I could use the property :lines in org-special-block? I
> > don't want to utilize #+ATTR_LATEX, since I'm aiming at extensions
> > to both LaTeX and HTML exporters recognizing this thing.
>
> What about #+attr_yourbackend ? E.g.,
>
> #+attr_yourbackend: :type mct
> - answer a
> - answer b
> - answer c
>
> or,
>
> #+attr_yourbackend: :lines 2
> #+begin_answer
> This is an answer.
> #+end_answer
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?
(Anyway, options after #+BEGIN_MYBLOCK would be a bit nicer, since the
user would not have to type /that/ much.)
> Another, more advanced option, is to use a parse tree filter to create
> pseudo-types, i.e., element or object types that don't exist in
> regular Org syntax. See `math-block' type in "ox-latex.el", in
> particular `org-latex-math-block-tree-filter'.
Thanks, I'll look into this!
I tried to look for math-block in ox-latex.el, but did not find it. I
have Org-mode from Elpa, org-version gives:
Org-mode version 8.2.5f
(8.2.5f-elpa @ /home/marcin/.emacs.d/elpa/org-20140116/)
Should I upgrade?
> Regards,
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
next prev parent reply other threads:[~2014-03-16 11:18 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 [this message]
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
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=20140316121832.2bc543c1@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--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).