emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andrea Lazzarini <andrea.lazzarini1@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: 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: Sat, 4 Mar 2023 16:43:11 +0100	[thread overview]
Message-ID: <05C874CC-D677-420F-98AF-313F5264E68B@gmail.com> (raw)
In-Reply-To: <9302738a-b351-0422-22ad-e764aade01e5@gmail.com>

I totally agree with Max Nikulin: wouldn't that be an improvement? That would make things a lot easier for those instances in which you want to put the footnotes back in.

> Il giorno 3 mar 2023, alle ore 17:47, Max Nikulin <manikulin@gmail.com> ha scritto:
> 
> On 03/03/2023 22:47, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>> Self-containing example:
>>> 
>>> ---- 8< ----
>>> #+options: f:nil
>>> 
>>> Pellentesque dapibus suscipit ligula.[fn::1 ftnt]  Donec posuere augue
>>> in quam.
>>> ---- >8 ----
>> This is because spaces after Org syntax objects are considered a part of
>> those syntax objects.  So, excluding footnote automatically means
>> excluding spaces after.
> 
> In my opinion, the filter removing footnotes should transfer afterspaces to preceding objects.
> 



  reply	other threads:[~2023-03-04 15:44 UTC|newest]

Thread overview: 22+ 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 [this message]
2023-03-05 12:06       ` Ihor Radchenko
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

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=05C874CC-D677-420F-98AF-313F5264E68B@gmail.com \
    --to=andrea.lazzarini1@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.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).