From mboxrd@z Thu Jan 1 00:00:00 1970 From: myq larson 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, 7 Jun 2015 23:44:35 -0600 Message-ID: References: <87d217vn1b.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11359d100898880517fb23ae Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59205) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1prT-0005TS-Os for emacs-orgmode@gnu.org; Mon, 08 Jun 2015 01:44:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z1prQ-0001WS-Af for emacs-orgmode@gnu.org; Mon, 08 Jun 2015 01:44:39 -0400 Received: from mail-qk0-f178.google.com ([209.85.220.178]:33329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z1prQ-0001W0-66 for emacs-orgmode@gnu.org; Mon, 08 Jun 2015 01:44:36 -0400 Received: by qkhg32 with SMTP id g32so72835265qkh.0 for ; Sun, 07 Jun 2015 22:44:35 -0700 (PDT) In-Reply-To: <87d217vn1b.fsf@nicolasgoaziou.fr> 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: emacs-orgmode@gnu.org --001a11359d100898880517fb23ae Content-Type: text/plain; charset=UTF-8 On Sun, Jun 7, 2015 at 4:19 AM, Nicolas Goaziou wrote: > 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. Hi Nicolas, 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. 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. Thank you for your help, Cheers, Myq --001a11359d100898880517fb23ae Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sun, Jun 7, 2015 at 4:19 AM, Nicolas Goaziou &l= t;mail@nicolasgoaziou.fr> = wrote:
> Hello,
>
> myq larson <myq@wordish.org> writes:
>
>> If there i= s an inline task at the end of a paragraph, when the document
>> i= s exported with the =3Dinlinetask=3D option set to =3Dnil=3D, the space aft= er
>> the inline task and before the next paragraph will be ignore= d and the
>> two paragraphs will combine as one.
>>
&g= t;> For example, this document
>>
>> #+BEGIN_EXAMPLE>> =C2=A0 ,#+OPTIONS: inline:nil toc:nil
>>
>> = =C2=A0 * title
>>
>> =C2=A0 =C2=A0 Here is some text whic= h should not be cut by an inline task because
>> =C2=A0 =C2=A0 it = should respect the linebreaks and understand when a new paragraph
>&g= t; =C2=A0 =C2=A0 starts.
>> =C2=A0 *************** TODO Fix this>> =C2=A0 It's not good, so fix this.
>> =C2=A0 ******= ********* END
>> =C2=A0 =C2=A0 I think this is the right way to go= . But there are some challenges.
>> =C2=A0 *************** TODO Th= is could be better
>> =C2=A0 *************** END
>>
&g= t;>
>> =C2=A0 =C2=A0 Another problem is that there is no way to= fix the problem.
>> #+END_EXAMPLE
>>
>> Exports= as:
>>
>> #+BEGIN_EXAMPLE
>> =C2=A0 ______
&= gt;>
>> =C2=A0 =C2=A0TEST
>>
>> =C2=A0 =C2=A0= me
>> =C2=A0 ______
>>
>>
>>
>&g= t;
>>
>> =C2=A0 1 title
>> =C2=A0 =3D=3D=3D=3D= =3D=3D=3D
>>
>> =C2=A0 =C2=A0 Here is some text which sho= uld not be cut by an inline task because it
>> =C2=A0 =C2=A0 shoul= d respect the linebreaks and understand when a new paragraph
>> = =C2=A0 =C2=A0 starts.
>> =C2=A0 =C2=A0 I think this is the right w= ay to go. But there are some challenges.
>> =C2=A0 =C2=A0 Another = problem is that there is no way to fix the problem.
>> #+END_EXAMP= LE
>>
>> I think there should be two paragraphs. Ideally,= the first paragraph
>> should refill as well.
>
> The= re are two paragraphs, albeit not separated by an empty line. The
> b= ehaviour is correct here.

Hi Nicolas,

Using that d= efinition though, there are probably three paragraphs. I choose
A= SCII 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<= /div>
which means the two paragraphs will be interpreted as a single
paragraph. 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
=C2=A0 ,#+OPTIONS: inline:nil toc:nil
=C2=A0 ,* title

=C2=A0 Here is some te= xt which should not be cut by an inline task because
=C2=A0 it sh= ould respect the linebreaks and understand when a new paragraph
= =C2=A0 starts.=C2=A0
=C2=A0 I think this is the right way to go. = But there are some challenges.
=C2=A0 Another problem is that the= re is no way to fix the problem.
#+END_EXAMPLE

I'm pretty sure that's not how Org mode defines two paragrap= hs though.
As a work around, I just avoid putting inline comments= at the end of
paragraphs.

Thank you for= your help,

Cheers,

Myq

--001a11359d100898880517fb23ae--