Article Mode eats newlines between src-blocks (was Re: org-element-at-point fails in programming-modes)

[Thorsten Jolitz <tjolitz@gmail.com>]

Nicolas Richard <theonewiththeevillook@yahoo.fr> writes:

> Thorsten Jolitz <tjolitz@gmail.com> writes:
>> Maybe they switched to the new parser between versions, that parses a
>> src-block with :post-blank's, but does not take them into account when
>> interpreting? 
>
> I tried an experiment : (defun org-mode (&rest _) t) and refresh. The
> newlines didn't come back (but fontification obviously disappeared). So
> I guess it isn't org-mode's fault.
>
> I would like to blame (mm-uu-dissect) but I didn't look into it. I'll
> take the opportunity to test if it'll also eat multiple blank lines (I
> think it will) :
>
> #+BEGIN_QUOTE
> hallo world
> #+END_QUOTE
> #+BEGIN_COMMENT
> hallo world
> #+END_COMMENT
> #+BEGIN_EXAMPLE
> hallo world
> #+END_EXAMPLE
> #+BEGIN_SRC emacs-lisp
> hallo world
> #+END_SRC
>
> (There should be 1, then 2, then 3 blanks lines between the successives
> blocks above.)

I don't see any blank lines between the blocks.

This is how a string that is fontified in mm-view.el looks like, no
matter if there are trailing blank lines:

,----
| "#+BEGIN_SRC emacs-lisp\n  (- 2 2)\n#+END_SRC\n"
`----

i.e. thats the value of HANDLE in this function:

,----
| (mm-display-inline-fontify HANDLE &optional MODE)
`----

So either they missed the additional final "\n"'s for all but the last
block when parsing, or they forgot to handle them when inserting the
fontified string again. 

PS

I renamed this thread because the original topic, which is still more
important for me (!), is not discussed anymore.

-- 
cheers,
Thorsten