From: Nicolas Goaziou <n.goaziou@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [new exporter] feature request: BEGIN_LATEX_HEADER
Date: Thu, 07 Mar 2013 22:05:43 +0100 [thread overview]
Message-ID: <87txomc448.fsf@gmail.com> (raw)
In-Reply-To: <874ngngs8c.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 7 Mar 2013 15:11:15 +0000")
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Prompted by Nicolas's recent addition of the LATEX_HEADER_EXTRA
> directive, I would like to request another related feature. Just as we
> have the related LATEX and BEGIN_LATEX directives, I would like to see a
> BEGIN_LATEX_HEADER directive for multi-line LATEX_HEADER lines:
>
> #+begin_src org
> #+BEGIN_LATEX_HEADER
> \usepackage{tikz}
> \usepackage[british]{babel}
> \newcommand{\esf}[1]{\footnote{#1}\marginpar{\fbox{\thefootnote}}
> #+END_LATEX_HEADER
> #+end_src
>
> (example taken from a recent org file).
>
> Not urgent, of course, but it would make it easier to write this type of
> content, especially if it were fontified as well... ;-)
There are already many ways to handle latex header. `org-latex-classes',
setupfile keywords, include keywords, latex_header,
latex_header_extra...
Adding one more is not without consequences. For example, where should
it go? After latex_header values? Before? Would the location be
configurable in `org-latex-classes'? What placeholder to use?
I admit I'm not very keen on this idea. Not because of the coding work,
it would be around 10 loc, but because of syntax fester.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-07 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 15:11 [new exporter] feature request: BEGIN_LATEX_HEADER Eric S Fraga
2013-03-07 21:05 ` Nicolas Goaziou [this message]
2013-03-07 23:40 ` Rasmus
2013-03-09 10:00 ` Eric S Fraga
2013-03-09 11:23 ` Achim Gratz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txomc448.fsf@gmail.com \
--to=n.goaziou@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.