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: Wed, 21 Jul 2021 21:48:37 +0700	[thread overview]
Message-ID: <sd9c46$p86$1@ciao.gmane.io> (raw)
In-Reply-To: <87y2a29z9l.fsf@ucl.ac.uk>

On 19/07/2021 21:03, Eric S Fraga wrote:
> On Friday, 16 Jul 2021 at 12:06, William Denton wrote:
>> People who write one-sentence-per-line, have you had this problem, and if so how
>> did you handle it?
> If I will be exporting to LaTeX, I do the following:
> --8<---------------cut here---------------start------------->8---
> One sentence is here.
> #+latex: % a sentence that has been commented out.
> The third sentence is here and should be in the same paragraph as the first.
> --8<---------------cut here---------------end--------------->8---
> The LaTeX directive is a LaTeX comment (% at the start) and so replaces
> what would otherwise be a blank line causing a new paragraph to start.
> It may not be pretty but it works just fine.

It is at least fragile. HTML export results in separate paragraphs:

One sentence is here.
The third sentence is here and should be in the same paragraph as the 

 > Empty lines and other elements end paragraphs.

I am unsure, but "#+latex:" probably belongs to "Keywords" that are 
elements, so it should end a paragraph. If such interpretation is 
correct than either LaTeX exporter has a bug or syntax description 
should be justified.

  reply	other threads:[~2021-07-21 14:49 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
2021-07-19 14:03 ` Eric S Fraga
2021-07-21 14:48   ` Maxim Nikulin [this message]
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='sd9c46$p86$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).