emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] feature request: BEGIN_LATEX_HEADER
Date: Sat, 9 Mar 2013 10:00:49 +0000	[thread overview]
Message-ID: <87hakk51v2.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87txomc448.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 7 Mar 2013 22:05:43 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> 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:

[...]

> 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 wasn't proposing anything different other than allowing one to group a
whole set of #+latex_header lines into a single begin/end block, akin to
what #+begin_latex allows.  Just a minor convenience feature.

> 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.

Okay, no worries.  Thanks for considering it.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org 7.9.3e-970-g728c0e

  parent reply	other threads:[~2013-03-09 10:01 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
2013-03-07 23:40   ` Rasmus
2013-03-09 10:00   ` Eric S Fraga [this message]
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

  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=87hakk51v2.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --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).