From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou 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 Message-ID: <87d217vn1b.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33799) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1XeI-0000yH-J0 for emacs-orgmode@gnu.org; Sun, 07 Jun 2015 06:17:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z1XeH-00035V-HW for emacs-orgmode@gnu.org; Sun, 07 Jun 2015 06:17:50 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:57803) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1XeH-0002xe-B6 for emacs-orgmode@gnu.org; Sun, 07 Jun 2015 06:17:49 -0400 In-Reply-To: (myq larson's message of "Sun, 7 Jun 2015 03:21:43 -0600") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: myq larson Cc: emacs-orgmode@gnu.org Hello, myq larson 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