org mode latex export excude title

org mode latex export excude title

[Fanpeng Kong]

I am trying to use org mode to write a paper. The latex template of the
journal restricts the location of `\title{}` command to be after the
`\begin{document}`. While by leaving `#+TITLE:` empty and specify
`#+OPTIONS: title:nil` in my org file, I can remove the `\maketitle` command in the
latex export. However, and empty title `\title{}` is still exported
prior to the `\begin{document}`. And it causes problem for the template
I am using.

Following is an minimal example of the org mode latex export. Is there
any way to excude the empty `\title{}` command?

\documentclass[10pt]{article}
\usepackage{}
...
\usepackage{}

\date{}
\title{}

\hypersetup{
}

\begin{document}
...
\end{document}

Any suggestion will be appreciated. And of course, Happy New Year!

Cheers
Fanpeng

Re: org mode latex export excude title

[Charles C. Berry]

On Fri, 30 Dec 2016, Fanpeng Kong wrote:

> I am trying to use org mode to write a paper. The latex template of the
> journal restricts the location of `\title{}` command to be after the
> `\begin{document}`. While by leaving `#+TITLE:` empty and specify
> `#+OPTIONS: title:nil` in my org file, I can remove the `\maketitle` command in the
> latex export. However, and empty title `\title{}` is still exported
> prior to the `\begin{document}`. And it causes problem for the template
> I am using.
>
> Following is an minimal example of the org mode latex export. Is there
> any way to excude the empty `\title{}` command?

[example deleted]

> Any suggestion will be appreciated. And of course, Happy New Year!

Use a filter to comment it out:



#+OPTIONS: title:nil toc:nil
#+BIND: org-export-filter-final-output-functions (comment-out-title-line)

#+BEGIN_SRC emacs-lisp :exports results :results none
   (defun comment-out-title-line (doc &optional bk info)
     (replace-regexp-in-string "\\\\title" "%% \\title" doc nil t ))
   (setq-local org-export-allow-bind-keywords t)
#+END_SRC



* section 1

...

HTH,

Chuck

Re: org mode latex export excude title

[Ken Mankoff]

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

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

Can be set as a buffer local variable.

  -k.

On Fri, Dec 30, 2016 at 12:26 PM, Charles C. Berry <ccberry@ucsd.edu> wrote:

> On Fri, 30 Dec 2016, Fanpeng Kong wrote:
>
> I am trying to use org mode to write a paper. The latex template of the
>> journal restricts the location of `\title{}` command to be after the
>> `\begin{document}`. While by leaving `#+TITLE:` empty and specify
>> `#+OPTIONS: title:nil` in my org file, I can remove the `\maketitle`
>> command in the
>> latex export. However, and empty title `\title{}` is still exported
>> prior to the `\begin{document}`. And it causes problem for the template
>> I am using.
>>
>> Following is an minimal example of the org mode latex export. Is there
>> any way to excude the empty `\title{}` command?
>>
>
> [example deleted]
>
> Any suggestion will be appreciated. And of course, Happy New Year!
>>
>
> Use a filter to comment it out:
>
>
>
> #+OPTIONS: title:nil toc:nil
> #+BIND: org-export-filter-final-output-functions (comment-out-title-line)
>
> #+BEGIN_SRC emacs-lisp :exports results :results none
>   (defun comment-out-title-line (doc &optional bk info)
>     (replace-regexp-in-string "\\\\title" "%% \\title" doc nil t ))
>   (setq-local org-export-allow-bind-keywords t)
> #+END_SRC
>
>
>
> * section 1
>
> ...
>
> HTH,
>
> Chuck
>
>

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

Re: org mode latex export excude title

[Charles C. Berry]

On Fri, 30 Dec 2016, Ken Mankoff wrote:

> (setq-local org-latex-title-command "")
>
> Can be set as a buffer local variable.
>

True, but not relevant to the OPs query:

>>> Is there any way to excude the empty `\title{}` command?

And if you browse thru org-latex-template, you will see that

 	 "\\title{%s%s}\n"

is hard coded.  The value of org-latex-title-command has no effect on that 
part of the template.

So, the OP can either use a filter as I suggested or write a derived 
backend supplying a different template transcoder that drops the string 
quoted above.

Chuck