emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander Baier <alexander.baier@mailbox.org>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Latex Export] Influence placement of \maketitle command
Date: Wed, 14 May 2014 23:28:53 +0200	[thread overview]
Message-ID: <87d2fgvylm.fsf@mailbox.org> (raw)
In-Reply-To: <874n0snq0p.fsf@alphaville.bos.redhat.com> (Nick Dokos's message of "Wed, 14 May 2014 15:01:26 -0400")

On 2014-05-14 21:01 Nick Dokos wrote:
> Alexander Baier <alexander.baier@mailbox.org> writes:
>> Hello,
>> I am writing a paper using llncs as the document class. I use the
>> =\institute= command which has to be placed _above_ the =\maketitle=
>> command to be considered. But exporting my document always yields a
>> latex file where =\maketitle= appears above =\institute=. I use
>> simple #+LATEX: directives to insert =\institute=.
>> Is there a way for me to influence the placement of =\maketitle= and
>> thus be able to order those commands "the right way"?
>> TIA for any pointers,
> If \institute can be placed in the preamble, then using #+LATEX_HEADER
> instead of #+LATEX is probably the way to go.

Of course! Somehow I totally forgot about the LATEX_HEADER
directive. With this, everything works fine!

> If it has to be in the document body, one way to do it is to redefine
> the variable org-latex-title-command in a file-local-variable section
> added to the end of your file:
> # Local Variables:
> # org-latex-title-command: "\\institute{Foo}\\maketitle"
> # End:

Oh, the title-command is a variable, that is nice.

Thank you very much,
Alexander Baier

  reply	other threads:[~2014-05-14 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 18:26 [Latex Export] Influence placement of \maketitle command Alexander Baier
2014-05-14 19:01 ` Nick Dokos
2014-05-14 21:28   ` Alexander Baier [this message]
2014-05-15 19:02   ` Alexander Baier
2014-05-15 19:57     ` Eric S Fraga
2014-05-15 20:41       ` Alexander Baier
2014-05-16  4:19         ` Nick Dokos
2014-05-16  8:36           ` Alexander Baier
2014-05-16  7:15         ` Eric S Fraga
2014-05-16  9:15           ` Alexander Baier

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:

  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=87d2fgvylm.fsf@mailbox.org \
    --to=alexander.baier@mailbox.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \


* 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


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