Buffer-local override of org-latex-title-command?

Buffer-local override of org-latex-title-command?

[James Harkins]

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

Re: Buffer-local override of org-latex-title-command?

[Thomas S. Dye]

Aloha James,

James Harkins <jamshark70@gmail.com> writes:

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

Does an empty #+TITLE: do what you want?

hth,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: Buffer-local override of org-latex-title-command?

[James Harkins]

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

On Apr 29, 2013 8:23 PM, "Thomas S. Dye" <tsd@tsdye.com> wrote:
>
> James Harkins <jamshark70@gmail.com> writes:
>
> > 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.
>
> Does an empty #+TITLE: do what you want?

No, because I do need the title, but inside the \twocolumn part. I wouldn't
be able to submit the manuscript with no title.

hjh

[-- Attachment #2: Type: text/html, Size: 776 bytes --]

Re: Buffer-local override of org-latex-title-command?

[Thomas S. Dye]

Aloha James,

James Harkins <jamshark70@gmail.com> writes:

> On Apr 29, 2013 8:23 PM, "Thomas S. Dye" <tsd@tsdye.com> wrote:
>>
>> James Harkins <jamshark70@gmail.com> writes:
>>
>> > 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.
>>
>> Does an empty #+TITLE: do what you want?
>
> No, because I do need the title, but inside the \twocolumn part. I wouldn't
> be able to submit the manuscript with no title.

If you use asynchronous export you can put this in the init.el
initialization file:

(setq org-latex-title-command "")

hth,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: Buffer-local override of org-latex-title-command?

[Nicolas Goaziou]

Hello,

James Harkins <jamshark70@gmail.com> writes:

> On Apr 29, 2013 8:23 PM, "Thomas S. Dye" <tsd@tsdye.com> wrote:
>>
>> James Harkins <jamshark70@gmail.com> writes:
>>
>> > 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.
>>
>> Does an empty #+TITLE: do what you want?
>
> No, because I do need the title, but inside the \twocolumn part. I wouldn't
> be able to submit the manuscript with no title.

Try:

  #+BIND: org-latex-title-command ""

This assumes `org-export-allow-bind-keywords' is non-nil.


Regards,

-- 
Nicolas Goaziou

Re: Buffer-local override of org-latex-title-command?

[Thomas S. Dye]

Aloha Nicolas,

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

> Hello,
>
> Try:
>
>   #+BIND: org-latex-title-command ""
>
> This assumes `org-export-allow-bind-keywords' is non-nil.

I couldn't find a reference to this variable in the manual.  I'd suggest
replacing the word `Eventually' with the clause before the first comma
in the paragraph below, or something like it.

  If the variable `org-export-allow-bind-keywords' is non-nil, Emacs
  variables can become buffer-local during export by using the BIND
  keyword. Its syntax is `#+BIND: variable value'. This is particularly
  useful for in-buffer settings that cannot be changed using specific
  keywords.

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: Buffer-local override of org-latex-title-command?

[Bastien]

Hi Thomas,

tsd@tsdye.com (Thomas S. Dye) writes:

> I couldn't find a reference to this variable in the manual.  I'd suggest
> replacing the word `Eventually' with the clause before the first comma
> in the paragraph below, or something like it.
>
>   If the variable `org-export-allow-bind-keywords' is non-nil, Emacs
>   variables can become buffer-local during export by using the BIND
>   keyword. Its syntax is `#+BIND: variable value'. This is particularly
>   useful for in-buffer settings that cannot be changed using specific
>   keywords.

Done, thanks.

-- 
 Bastien

Re: Buffer-local override of org-latex-title-command?

[James Harkins]

[-- Attachment #1: Type: text/plain, Size: 311 bytes --]

On Apr 29, 2013 10:08 PM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> Try:
>
>   #+BIND: org-latex-title-command ""
>
> This assumes `org-export-allow-bind-keywords' is non-nil.

Oh, ok, I thought I'd tried something like that but I guess I didn't get
all the moving parts in the right place. Thanks!

hjh

[-- Attachment #2: Type: text/html, Size: 482 bytes --]