From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Trailing whitespace after export snippets without a transcoder
Date: Mon, 22 Apr 2024 17:45:44 +0700 [thread overview]
Message-ID: <v05f4q$a6m$1@ciao.gmane.io> (raw)
In-Reply-To: <87wmoqq3ad.fsf@localhost>
On 21/04/2024 20:00, Ihor Radchenko wrote:
> Max Nikulin writes:
>> A space@@ascii:*@@ character.
>
> Hmm. We actually have a similar scenario in `org-export--prune-tree'
> with a slightly different logic - only keep spaces when previous object
> does not have any.
I like this idea. At first I even believed that backend-specific code
would not be necessary.
> I do not think that we need to handle this Org mode-wide (it will be
> difficult and will likely cause breaking changes).
I have not figured out why it may become a breaking changes and what
backends need blank lines inside paragraph. I would make stripping empty
lines default behavior with some option to disable this feature.
> See the attached tentative fix.
Since zero width spaces are part of Org syntax, they need special treatment.
---- 8< ----
#+macro: empty (eval "")
Some *bold*@@comment: *@@ text.
@@comment: line@@
More /italic/{{{empty}}} text.
{{{empty}}}
Last line.
---- >8 ----
LaTeX export:
---- 8< ----
Some \textbf{bold}text.
More \emph{italic} text.
Last line.
---- >8 ----
Notice visible space character disappeared after "bold". I am leaving up
to you to decide if empty line appeared due to a macro is a bug or a
feature. If I remember it correctly, your opinion is that a macro
expanding to multiple paragraphs is a valid one.
next prev parent reply other threads:[~2024-04-22 10:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 0:04 Inline comments ypuntot
2023-06-22 1:50 ` Max Nikulin
2023-06-28 15:51 ` [PATCH] org-faq.org: " Max Nikulin
2023-06-29 10:47 ` Ihor Radchenko
2023-06-30 10:34 ` Max Nikulin
2023-07-01 10:48 ` Ihor Radchenko
2023-08-06 18:34 ` Bastien Guerry
2023-07-01 15:24 ` Ihor Radchenko
2023-07-02 5:46 ` Org FAQ design (Re: [PATCH] org-faq.org: Inline comments) Max Nikulin
2023-07-08 5:48 ` [PATCH v2] org-faq.org: Inline comments Max Nikulin
2023-07-08 9:31 ` Ihor Radchenko
2023-07-10 16:09 ` Max Nikulin
2023-09-01 11:28 ` Ihor Radchenko
2024-04-15 12:17 ` Ihor Radchenko
2024-04-17 14:44 ` Max Nikulin
2024-04-20 11:14 ` Trailing whitespace after export snippets without a transcoder (was: [PATCH v2] org-faq.org: Inline comments) Ihor Radchenko
2024-04-20 15:02 ` Trailing whitespace after export snippets without a transcoder Max Nikulin
2024-04-21 13:00 ` Ihor Radchenko
2024-04-22 10:45 ` Max Nikulin [this message]
2024-04-22 19:01 ` Ihor Radchenko
2024-04-25 10:54 ` Max Nikulin
2024-04-28 11:19 ` Ihor Radchenko
2024-05-19 10:04 ` 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='v05f4q$a6m$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).