emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: Andrea Lazzarini <andrea.lazzarini1@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] No space after footnote with org-export-with-footnotes set to nil [9.6.1 ( @ /Users/test/.emacs.d/elpa/28.0/develop/org-9.6.1/)]
Date: Sun, 05 Mar 2023 12:06:52 +0000	[thread overview]
Message-ID: <87o7p7z9k3.fsf@localhost> (raw)
In-Reply-To: <9302738a-b351-0422-22ad-e764aade01e5@gmail.com>

Max Nikulin <manikulin@gmail.com> writes:

> In my opinion, the filter removing footnotes should transfer afterspaces 
> to preceding objects.

I am not sure.

Consider text like "Pellentesque dapibus suscipit ligula. [fn:1] Donec posuere augue in quam."
with space before the footnote. If we replace the footnote with space,
two spaces will be exported. I am not sure if it is expected.

Also, should we replace footnote with a single space or with the number
of spaces after?

Further, this bug is actually not just about footnotes. The footnotes
are removed in `org-export--prune-tree':

    (if (org-export--skip-p data info selected excluded)
    		      (if (memq type '(table-cell table-row)) (push data ignore)
    			(org-element-extract-element data))

The extracted objects can be latex-fragment, statistics-cookie,
timestamp, and footnote.

Will it be safe to replace all the above with space? Or maybe with
number of spaces equal to :post-blank? Something else?

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  parent reply	other threads:[~2023-03-05 12:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 10:07 [BUG] No space after footnote with org-export-with-footnotes set to nil [9.6.1 ( @ /Users/test/.emacs.d/elpa/28.0/develop/org-9.6.1/)] Andrea Lazzarini
2023-03-03 14:44 ` Max Nikulin
2023-03-03 15:47   ` Ihor Radchenko
2023-03-03 16:47     ` Max Nikulin
2023-03-04 15:43       ` Andrea Lazzarini
2023-03-05 12:06       ` Ihor Radchenko [this message]
2023-03-05 12:32         ` Andrea Lazzarini
2023-03-05 12:42           ` Ihor Radchenko
2023-03-05 12:54             ` Andrea Lazzarini
2023-03-05 13:01               ` Ihor Radchenko
2023-03-06 12:18                 ` Max Nikulin
2023-03-07 13:59                   ` Ihor Radchenko
2023-03-08 15:14                     ` Max Nikulin
2023-03-09 12:43                       ` Ihor Radchenko
2023-03-09 15:04                         ` Max Nikulin
2023-03-10 12:08                           ` Ihor Radchenko
2023-03-10 14:03                             ` Max Nikulin
2023-03-11 10:38                               ` Ihor Radchenko
2023-03-13 15:17                                 ` Max Nikulin
2023-03-14 12:19                                   ` Ihor Radchenko
2023-03-27 14:16                                 ` Ihor Radchenko
2023-04-14 11:47                                   ` Ihor Radchenko
2024-04-24 16:07                                   ` Max Nikulin

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=87o7p7z9k3.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=andrea.lazzarini1@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \


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