From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ANN] ox-extras
Date: Mon, 23 Jun 2014 00:08:40 +0200 [thread overview]
Message-ID: <87bntkvbpz.fsf@gmx.us> (raw)
In-Reply-To: 87ionsvbsl.fsf@gmx.us
Rasmus <rasmus@gmx.us> writes:
> Aaron Ecay <aaronecay@gmail.com> writes:
>
>> 2014ko ekainak 21an, Aaron Ecay-ek idatzi zuen:
>>
>> [...]
>>
>>>> Eventually, if you insist on writing your full preamble within the
>>>> document, you can start to write it in a LaTeX-mode buffer, copy it in
>>>> your Org document and add "#+LATEX_HEADER: " in front of each line.
>>>> This last step is done easily with `string-rectangle' (C-x r t).
>>>
>>> This is basically making the user do (something like) org-edit-special
>>> manually. It can probably be automated somewhat – I’ll work on a
>>> patch.
>>
>> This is now implemented in a new library in contrib, ox-extras. This is
>> intended as a semi-official, semi-curated repository for helpful pieces of
>> org export hooks and customizations. Differently than worg, the aim is to
>> make it easy for users to load the snippets through the ox-extras-activate
>> function. Even so, I hope this will be an “executable wiki” where anyone
>> (who has commit access to the org repo) is free to contribute new hook
>> functions and improve existing ones.
>>
>> In the present case, if you execute
>>
>> (ox-extras-activate '(latex-header-blocks))
>>
>> you will be able to use blocks of the following form:
>>
>> #+header: :header yes
>> #+begin_latex
>>
>> \foo{}
>> \bar{}
>> #+end_latex
>>
>> These will be transformed so that the begin/end wrapper is removed and
>> each line is prepended with #+latex_header: on export. They can be
>> edited as latex code with the usual org-edit-special function (C-c ').
>>
>> The #+header: :header yes line is a bit confusing. The first #+header:
>> is part of org syntax that allows us to tag blocks (and other elements)
>> with plists. The :header yes in the plist indicates that this block
>> should be treated as a latex_header, and not a normal type of latex
>> block.
>
> You did not attach a file and you probably want to make it as s new
> message without the ref to the previous thread.
Sorry, it's in contrib as you said :) My mistake.
--
Bang bang
next prev parent reply other threads:[~2014-06-22 22:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 23:37 BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-19 23:48 ` Aaron Ecay
2014-06-20 7:51 ` Sebastien Vauban
2014-06-20 8:50 ` Nicolas Goaziou
2014-06-20 11:17 ` Ken Mankoff
2014-06-20 11:52 ` Fabrice Popineau
2014-06-20 12:11 ` Nicolas Goaziou
2014-06-21 5:43 ` Aaron Ecay
2014-06-21 8:16 ` Nicolas Goaziou
2014-06-22 0:42 ` Aaron Ecay
2014-06-22 2:00 ` [ANN] ox-extras (was: BEGIN_LATEX_HEADER [cont]) Aaron Ecay
2014-06-22 22:07 ` [ANN] ox-extras Rasmus
2014-06-22 22:08 ` Rasmus [this message]
2014-06-23 19:57 ` Nicolas Goaziou
2014-06-23 20:29 ` Thomas S. Dye
2014-06-22 2:19 ` BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-22 9:36 ` Nicolas Goaziou
2014-06-22 9:35 ` 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=87bntkvbpz.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).