emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Comments break up a paragraph when writing one-setence-per-line
Date: Sun, 18 Jul 2021 15:21:39 +0700	[thread overview]
Message-ID: <sd0oak$k5h$1@ciao.gmane.io> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2107161156080.74845@shell3.miskatonic.org>

On 16/07/2021 23:06, William Denton wrote:
> #+begin_src org
> In this paragraph I introduce an idea.
> # Here is something I'm not sure about yet.
> But I am sure about this.
> And here is my conclusion.
> #+end_src org
> When this is exported, it becomes two paragraphs, as though the 
> commented line was a blank line.  This was unexpected, because to me 
> this is one paragraph with one sentence hidden.
> People who write one-sentence-per-line, have you had this problem, and 
> if so how did you handle it?

This is unexpected and inconvenient for me as well. However it may be 
considered consistent with

> Empty lines and other elements end paragraphs.

I do not write one-sentence-per-line, but I do not think it matters at 
all. As a workaround I can suggest the following hack

#+macro: comment

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

  parent reply	other threads:[~2021-07-18  8:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 16:06 Comments break up a paragraph when writing one-setence-per-line William Denton
2021-07-16 16:34 ` Bruce D'Arcus
2021-07-16 18:10   ` Kaushal Modi
2021-07-17  1:50     ` Samuel Wales
2021-07-18  8:21 ` Maxim Nikulin [this message]
2021-07-19 14:03 ` Eric S Fraga
2021-07-21 14:48   ` Maxim Nikulin
2021-07-21 15:22     ` Eric S Fraga
2021-07-21 16:13       ` Maxim Nikulin
2021-10-02 17:57         ` Tom Gillespie
2021-10-03 11:34           ` 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:

  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='sd0oak$k5h$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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