emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Buffer-local override of org-latex-title-command?
Date: Mon, 29 Apr 2013 06:31:46 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130429T082901-292@post.gmane.org> (raw)

Hi,

I've decided to write my next research article using org's LaTeX
export. The first problem: the journal mandates one column for the
title/author heading and the abstract, while the remainder of the text
should be in two columns.

TeX FAQ recommends the following [1]:

\documentclass[twocolumn]{article}
...
\begin{document}
... % \author, etc
\twocolumn[
  \begin{@twocolumnfalse}
    \maketitle
    \begin{abstract}
      ...
    \end{abstract}
  \end{@twocolumnfalse}
]

I can get very near to that this way:

#+LaTeX: \twocolumn[ \begin{@twocolumnfalse} \maketitle
#+BEGIN_abstract
This is my abstract. This is my abstract.
This is my abstract. This is my abstract.
#+END_abstract
#+LaTeX: \end{@twocolumnfalse} ]

... followed by outline headings marking sections.

The problem is that the "org-latex-title-command" variable places
\maketitle before the \twocolumn[...] bit. I realize I can customize
the variable and make it an empty string, but I'm not sure I want this
to take effect for every document I export to LaTeX.

Is there a way to clear this variable that is local to the buffer?

hjh

[1] http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs

             reply	other threads:[~2013-04-29  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29  6:31 James Harkins [this message]
2013-04-29 12:21 ` Buffer-local override of org-latex-title-command? Thomas S. Dye
2013-04-29 12:26   ` James Harkins
2013-04-29 13:00     ` Thomas S. Dye
2013-04-29 14:08     ` Nicolas Goaziou
2013-04-29 17:04       ` Thomas S. Dye
2013-04-29 17:11         ` Bastien
2013-04-30  1:41       ` James Harkins

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=loom.20130429T082901-292@post.gmane.org \
    --to=jamshark70@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 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).