emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Sun, 07 Jun 2015 12:19:12 +0200	[thread overview]
Message-ID: <87d217vn1b.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAKj87xtfMBiy1xQBTrQ5SoSX+1aGfDxgAL5MTLOe14hKtfDdnw@mail.gmail.com> (myq larson's message of "Sun, 7 Jun 2015 03:21:43 -0600")

Hello,

myq larson <myq@wordish.org> writes:

> If there is an inline task at the end of a paragraph, when the document
> is exported with the =inlinetask= option set to =nil=, the space after
> the inline task and before the next paragraph will be ignored and the
> two paragraphs will combine as one.
>
> For example, this document
>
> #+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.
>   *************** TODO Fix this
>   It's not good, so fix this.
>   *************** END
>     I think this is the right way to go. But there are some challenges.
>   *************** TODO This could be better
>   *************** END
>
>
>     Another problem is that there is no way to fix the problem.
> #+END_EXAMPLE
>
> Exports as:
>
> #+BEGIN_EXAMPLE
>   ______
>
>    TEST
>
>     me
>   ______
>
>
>
>
>
>   1 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 think there should be two paragraphs. Ideally, the first paragraph
> should refill as well.

There are two paragraphs, albeit not separated by an empty line. The
behaviour is correct here.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-06-07 10:17 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 [this message]
2015-06-08  5:44   ` myq larson
2015-06-08  6:30     ` Nicolas Goaziou

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=87d217vn1b.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).