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/)]

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]

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.

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.10.8)
 of 2015-06-01 on toshiba
Package: Org-mode version 8.2.10 (release_8.2.10 @
/usr/local/share/emacs/24.5/lisp/org/)

current state:
==============
(setq
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-html-format-inlinetask-function 'ignore
 org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
     org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
 org-cycle-hide-inline-tasks org-cycle-show-empty-lines
 org-optimize-window-after-visibility-change)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-babel-pre-tangle-hook '(save-buffer)
 org-occur-hook '(org-first-headline-recenter)
 org-font-lock-hook '(org-inlinetask-fontify)
 org-html-format-headline-function 'ignore
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-latex-format-drawer-function '(lambda (name contents) contents)
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207"
  [org-add-hook change-major-mode-hook org-show-block-all append local] 5]
#[nil "\300\301\302\303\304$\207"
  [org-add-hook change-major-mode-hook org-babel-show-result-all append
   local]
  5]
org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-ascii-format-drawer-function '(lambda (name contents width) contents)
 org-html-format-drawer-function '(lambda (name contents) contents)
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-latex-format-inlinetask-function 'ignore
 org-confirm-shell-link-function 'yes-or-no-p
 )

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/)]

[Nicolas Goaziou]

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

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/)]

[myq larson]

[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]

On Sun, Jun 7, 2015 at 4:19 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> 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.

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

[-- Attachment #2: Type: text/html, Size: 3732 bytes --]

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/)]

[Nicolas Goaziou]

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,