From: Jakob Rosenblattl via Emacs-orgmode <emacs-orgmode@gnu.org>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Bug: `#+OPTIONS: <:nil' has no effect when exporting to LaTeX [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)]
Date: Tue, 13 Aug 2019 09:08:37 +0000 [thread overview]
Message-ID: <Eth2EyULczcYdB6z9YKj1LOj3pvSWdOqofWNZyO0LDZaYtvJntgL_erLvi4CUfoMl6T8lDFDWu8XQr3HFiJSB3Tc5Z51MXB786QnXRkXP_c=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
When I export to LaTeX, the created LaTeX file contains \date{\today}.
However, I don't want it to show the date. Using #+OPTIONS: date:nil
the LaTeX result will contain \date{} instead, which indeed hides the
date, but now there's empty space in place of the date when compiled to
a PDF document, which is undesirable. As per the manual the argument <
to the OPTIONS keyword is supposed to "[t]oggle inclusion of time/date
active/inactive stamps (org-export-with-timestamps)". Putting
#+OPTIONS: <:nil, however, has no effect at all; \date{\today} will
still end up in the LaTeX export.
Do I misunderstand the meaning of the argument <? How can I prevent the
awkward space in the final PDF where the date would normally be?
Thank you!
Emacs : GNU Emacs 26.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.8)
of 2019-04-12
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)
[-- Attachment #2: Type: text/html, Size: 1227 bytes --]
next reply other threads:[~2019-08-13 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 9:08 Jakob Rosenblattl via Emacs-orgmode [this message]
2019-08-13 12:31 ` Bug: `#+OPTIONS: <:nil' has no effect when exporting to LaTeX [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/)] Fraga, Eric
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='Eth2EyULczcYdB6z9YKj1LOj3pvSWdOqofWNZyO0LDZaYtvJntgL_erLvi4CUfoMl6T8lDFDWu8XQr3HFiJSB3Tc5Z51MXB786QnXRkXP_c=@protonmail.com' \
--to=emacs-orgmode@gnu.org \
--cc=jakob.rosenblattl@protonmail.com \
/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).