From: Ihor Radchenko <email@example.com>
To: Phil Estival <firstname.lastname@example.org>
Subject: Re: [PATCH] ox: fix comment exported as a blank line
Date: Mon, 04 Jul 2022 19:47:07 +0800 [thread overview]
Message-ID: <87k08tnlqc.fsf@localhost> (raw)
Phil Estival <email@example.com> writes:
> * lisp/ox.el (org-export--skip-p): no longer export single-line
> comments as blank lines which did break paragraphs in two.
I think that this change may be useful in general. `org-export--skip-p'
is sometimes too rigid.
However, the proposed feature should probably be added as a
customization that is not enabled by default.
prev parent reply other threads:[~2022-07-04 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 5:30 [PATCH] ox: fix comment exported as a blank line Phil Estival
2022-06-01 5:43 ` [PATCH] test-ox: no superfluous newline in exported comments Phil Estival
2022-06-01 11:48 ` [PATCH] ox: fix comment exported as a blank line Max Nikulin
2022-06-02 5:02 ` Phil Estival
2022-06-02 16:09 ` Max Nikulin
2022-06-01 13:14 ` Kaushal Modi
2022-07-04 11:47 ` Ihor Radchenko [this message]
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 \
* 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).