emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Phil Estival <pe@7d.nz>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox: fix comment exported as a blank line
Date: Thu, 2 Jun 2022 23:09:04 +0700	[thread overview]
Message-ID: <e384d381-0a60-f777-b285-e0b8e62b14a9@gmail.com> (raw)
In-Reply-To: <20b5709c-0def-c898-a0db-40322b5a3f1b@7d.nz>

On 02/06/2022 12:02, Phil Estival wrote:
> Still, the writing experience is much improved
> when comments are allowed inside paragraphs
> without disrupting the publication, and this
> definitely worth a few modifications.

There are at least a couple of workarounds for inline comments, however 
some care is required to not add a spurious blank line (I think, 
ox-latex should strip blank lines from paragraphs).

Maxim Nikulin. Re: Comments break up a paragraph when writing 
one-setence-per-line. Sun, 18 Jul 2021 15:21:39 +0700. 

#+macro: comment

Another test
{{{comment(some text
)}}} with macro comment.


Export snippets
@@c: a comment
@@ may be used with any non-existing backend name.

I believe that comments breaking paragraphs is an unnecessary pitfall. 
While comments are not passed to exporters there are should be no great 
problems besides users who rely on current behavior. I am unsure how 
many of them do it intentionally. Attributes and other keywords are more 
tricky case, but rather independent of comments.

  reply	other threads:[~2022-06-02 16:10 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 [this message]
2022-06-01 13:14 ` Kaushal Modi
2022-07-04 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:

  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=e384d381-0a60-f777-b285-e0b8e62b14a9@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pe@7d.nz \


* 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).