From: Max Nikulin <manikulin@gmail.com>
To: Andrea Lazzarini <andrea.lazzarini1@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: Mon, 6 Mar 2023 19:18:37 +0700 [thread overview]
Message-ID: <2b73ed2c-214b-36f9-d695-9137a37a88f3@gmail.com> (raw)
In-Reply-To: <875ybfz71b.fsf@localhost>
On 05/03/2023 20:01, Ihor Radchenko wrote:
> Consider
>
> * Heading [0/1] text
...
> Text with newline\\
> [footnote] more text.
...
> Text (parens[footnote] ).
I am not convinced that space should be dropped here.
> It might be enough to use spaces if and only if there are no preceding
> spaces. Or not. One may think of other edge cases.
An idea: retain :post-blank having more spaces. Newline > tab, tab = 8
spaces.
Ihor, could you, please, be more specific concerning languages where
spaces may be used before footnote marks? I would expect at least
non-breakable spaces, but they are not stripped currently.
next prev parent reply other threads:[~2023-03-06 12:19 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
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 [this message]
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:
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=2b73ed2c-214b-36f9-d695-9137a37a88f3@gmail.com \
--to=manikulin@gmail.com \
--cc=andrea.lazzarini1@gmail.com \
--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
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).