emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Anderson <kluwak@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Possible LaTeX export bug: Footnotes in items
Date: Mon, 22 Jan 2024 15:42:34 -0500	[thread overview]
Message-ID: <CAE7YrOW5+ZBtsyaVkyJAD9ZEkWsJQ3F0Ut543CSPkqmUTzhLhQ@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]

Hi All,

I'm new to the developers' mailing list, so I hope this is the right place
to post potential bugs.  I don't claim to know exactly why, but at least
for certain TOC options, the LaTeX exporter produces invalid code for item
titles containing footnotes.  I've attached a minimal (non)working example.

The resulting LaTeX code (also attached) uses \footnote inside \section and
\paragraph macros, producing compiler errors.  A little googling turns up
the following comp.text.tex usenet post
explaining that \footnote is fragile and cannot be used in those contexts
without \protect.  Manually adding \protect before \footnote in the
automatically-generated tex file appears to produce correct results.

I don't know if the best fix is to always \protect \footnotes in LaTeX
export, or if more contextual smarts are required, but this seems like an
issue worth addressing.

Eric Anderson

[-- Attachment #1.2: Type: text/html, Size: 1237 bytes --]

[-- Attachment #2: org-bug-mwe.org --]
[-- Type: application/octet-stream, Size: 73 bytes --]

#+OPTIONS: toc:nil H:6
* a [fn:: note a]
** b
*** b
**** d [fn:: note b]

[-- Attachment #3: org-bug-mwe.tex --]
[-- Type: application/octet-stream, Size: 847 bytes --]

% Created 2024-01-22 Mon 15:34
% Intended LaTeX compiler: pdflatex
\author{Eric Anderson}
 pdfauthor={Eric Anderson},
 pdfcreator={Emacs 27.2 (Org mode 9.6.9)}, 


\section{a \footnote{note a}}
\paragraph{d \footnote{note b}}

             reply	other threads:[~2024-01-22 21:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 20:42 Eric Anderson [this message]
2024-01-24 12:11 ` [BUG] Footnotes in section titles Ihor Radchenko
2024-01-24 14:14   ` Max Nikulin
2024-01-24 15:23     ` Juan Manuel Macías
2024-01-24 15:31       ` Colin Baxter
2024-01-24 15:41         ` Juan Manuel Macías
2024-01-26 12:53           ` Ihor Radchenko
2024-01-26 13:17             ` Juan Manuel Macías
2024-01-26 16:43             ` Max Nikulin
2024-02-01 14:44               ` [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) (was: [BUG] Footnotes in section titles) Ihor Radchenko
2024-02-01 17:44                 ` [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc) Juan Manuel Macías
2024-02-01 17:57                   ` Marvin Gülker
2024-02-02 17:00                   ` Ihor Radchenko
2024-02-02 17:12                     ` Marvin Gülker
2024-02-02 17:49                       ` Ihor Radchenko
2024-02-02 18:10                     ` Juan Manuel Macías
2024-02-02 20:21                       ` Exporting multiple #+AUTHOR keywords (was: [DISCUSSION] Allowing footnote-references inside parsed keywords (#+AUTHOR, #+TITLE, etc)) Ihor Radchenko
2024-02-02 22:26                         ` Exporting multiple #+AUTHOR keywords Juan Manuel Macías
2024-02-04 15:21                           ` Ihor Radchenko
2024-02-04 16:16                             ` Max Nikulin
2024-02-04 22:13                               ` Juan Manuel Macías
2024-02-05 14:57                               ` Ihor Radchenko
2024-01-26 12:09     ` [BUG] Footnotes in section titles Ihor Radchenko
2024-02-09 16:41       ` Ihor Radchenko

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:

  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=CAE7YrOW5+ZBtsyaVkyJAD9ZEkWsJQ3F0Ut543CSPkqmUTzhLhQ@mail.gmail.com \
    --to=kluwak@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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