emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Jeremie Juste <jeremiejuste@gmail.com>
To: Flavio Leonardo Cavalcanti de Moura <contato@flaviomoura.mat.br>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to avoid \title{} and \date{} in latex export
Date: Thu, 11 Apr 2019 21:32:11 +0200	[thread overview]
Message-ID: <87sguofidg.fsf@gmail.com> (raw)
In-Reply-To: <CAOsg_PSh=hKvDoQH4OXU9-O3+ZiyK-qugrk-BXU=xUJUot3vGQ@mail.gmail.com> (Flavio Leonardo Cavalcanti de Moura's message of "Wed, 10 Apr 2019 12:24:58 -0300")


Hello Flavio,

I believe you meant

#+OPTIONS:    date:nil title:nil

Notice the "s" at the end of option

Hope this helps,

Jeremie

Flavio Leonardo Cavalcanti de Moura <contato@flaviomoura.mat.br> writes:

> Hello,
>
> My org file uses a latex class that, after exporting, is in conflict with
> the lines \date{} and \title{} automatically generated by orgmode latex
> export. I already tried the following headings for the org file:
>
> 1.
>  #+TITLE:
> #+DATE:
>
> 2.
> #+TITLE:
>
> #+option: date:nil
>
> 3.
>
> #+option: title:nil date:nil
>
> But in all cases the lines
> \title{}
> \date{}
> are in the tex file automatically generated by the export engine. Is there
> a way to prevent the addition of these lines?
>
> Best regards,
> Flávio.

next prev parent reply	other threads:[~2019-04-11 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 15:24 How to avoid \title{} and \date{} in latex export Flavio Leonardo Cavalcanti de Moura
2019-04-11 19:32 ` Jeremie Juste [this message]
2019-04-11 20:58   ` Flavio Leonardo Cavalcanti de Moura
  -- strict thread matches above, loose matches on Subject: below --
2019-04-10 16:10 Flavio Leonardo Cavalcanti de Moura
2019-04-10 18:30 ` Julius Dittmar
2019-04-11  1:15 ` Leslie Watter
2019-04-10 21:27 Flavio Leonardo Cavalcanti de Moura
2019-04-11  4:01 ` Nick Dokos
2019-04-11  7:26   ` Georgios Kaklamanos

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=87sguofidg.fsf@gmail.com \
    --to=jeremiejuste@gmail.com \
    --cc=contato@flaviomoura.mat.br \
    --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

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