From: Max Nikulin <manikulin@gmail.com>
To: 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, 13 Mar 2023 22:17:56 +0700 [thread overview]
Message-ID: <tuner6$105d$1@ciao.gmane.io> (raw)
In-Reply-To: <87zg8jwp26.fsf@localhost>
On 11/03/2023 17:38, Ihor Radchenko wrote:
>
> Newlines are tricky. They may or may not be significant.
> For example, in CJK paragraphs, newlines are to be stripped.
>
> I think that a reasonable thing to do could be not adding newlines if
> the previous object is a plain string ending with a newline.
It is in agreement with my expectation that the fix should not be
LaTeX-specific. That is why I raised the issue in this thread.
> This is latex-specific.
> See the attached tentative fix.
> Reported-by: Max Nikulin <manikulin@gmail.com>
> Link: https://orgmode.org/list/tufdb6$11h2$1@ciao.gmane.io
and Max Nikulin to emacs-orgmode. Re: Comments break up a paragraph when
writing one-setence-per-line. Sun, 3 Oct 2021 18:34:10 +0700.
https://list.orgmode.org/sjc4fk$76r$1@ciao.gmane.io
> + (replace-regexp-in-string
> + (rx (1+ (0+ space) "\n")) "\n"
> + contents))
What I do not like with this regexp is that it matches every newline
character, not only blank lines:
(replace-regexp-in-string
(rx (1+ (0+ space) "\n")) "[n]"
"a \nb")
"a[n]b"
If you still believe that a fix should be for LaTeX only then I would
consider extra "\n": (rx "\n" (1+ (0+ space) "\n"))
I have realized that the following is a kind of pitfall in Org syntax:
#+macro: comment
Another
{{{comment(Paragraph separator! Do you expect it?)}}}
paragraph.
next prev parent reply other threads:[~2023-03-13 15: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
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 [this message]
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='tuner6$105d$1@ciao.gmane.io' \
--to=manikulin@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).