emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: William Denton <wtd@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Comments break up a paragraph when writing one-setence-per-line
Date: Mon, 19 Jul 2021 15:03:34 +0100	[thread overview]
Message-ID: <87y2a29z9l.fsf@ucl.ac.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2107161156080.74845@shell3.miskatonic.org> (William Denton's message of "Fri, 16 Jul 2021 12:06:54 -0400 (EDT)")

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.

HTH,
eric

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-598-g604bfd
: Latest paper written in org: https://arxiv.org/abs/2106.05096


  parent reply	other threads:[~2021-07-19 14:09 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 [this message]
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:
  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=87y2a29z9l.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=wtd@pobox.com \
    /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).