From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: myq larson <myq@wordish.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Inlinetask at end of paragraph causes two paragraphs to merge [8.2.10 (8.2.10-41-g42228a-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150601/)]
Date: Mon, 08 Jun 2015 08:30:08 +0200 [thread overview]
Message-ID: <877freogpb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAKj87xucAsB6PYNQ9OcyUDC9gqJFQFNaBgyz5r88yH0GqnNAiw@mail.gmail.com> (myq larson's message of "Sun, 7 Jun 2015 23:44:35 -0600")
myq larson <myq@wordish.org> writes:
> Using that definition though, there are probably three paragraphs. I choose
> ASCII export as the easiest example to show in email, but exporting to
> LaTeX shows the problem more clearly. There will not be two new lines
> which means the two paragraphs will be interpreted as a single
> paragraph.
Correct. As a feature, ox-latex preserves blank lines between elements,
which means they will be treated as a single paragraph in LaTeX.
> I believe the above ASCII example will be interpreted as a
> single paragraph by most readers as well.
>
> Exporting to Org mode gives the following:
>
> #+BEGIN_EXAMPLE
> ,#+OPTIONS: inline:nil toc:nil
>
> ,* title
>
> Here is some text which should not be cut by an inline task because
> it should respect the linebreaks and understand when a new paragraph
> starts.
> I think this is the right way to go. But there are some challenges.
> Another problem is that there is no way to fix the problem.
> #+END_EXAMPLE
>
> I'm pretty sure that's not how Org mode defines two paragraphs though.
> As a work around, I just avoid putting inline comments at the end of
> paragraphs.
You should simply add an empty line between a paragraph and the
inlinetask.
Regards,
prev parent reply other threads:[~2015-06-08 6:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 9:21 Bug: Inlinetask at end of paragraph causes two paragraphs to merge [8.2.10 (8.2.10-41-g42228a-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150601/)] myq larson
2015-06-07 10:19 ` Nicolas Goaziou
2015-06-08 5:44 ` myq larson
2015-06-08 6:30 ` Nicolas Goaziou [this message]
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=877freogpb.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=myq@wordish.org \
/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).