Denis Bitouzé <dbitouze-39zsbgiqgt5gwvitb5q...@public.gmane.org> writes:
> Well, please, don't trust me too quickly :) I must admit I'm very far
> from a mardown expert: I'm only a very occasional user.
I never use markdown myself. Between the two of us, you are de facto the
expert.
> In fact, my suggestion was wrong: AFAICS, the last example doesn't give
> the expected HTML result neither and the less bad solution for nested
> lists in markdown seems to be:
>
> #+NAME: test.md
> #+begin_src markdown
> - Foo 1
>
> - Foo 2:
>
> - Foo 21
> - Foo 22
>
> End of Foo 2 item.
> #+end_src
>
> which is interpreted as (rather ugly):
>
> #+begin_src html
> <ul>
> <li>
> <p>Foo 1:</p>
> </li>
> <li>
> <p>Foo 2:</p>
> <ul>
> <li>Foo 21</li>
> <li>Foo 22</li>
> </ul>
> <p>End of Foo 2 item.</p>
> </li>
> </ul>
> #+end_src
This is problematic. There is a rule in "ox-md" that contradicts what
you are suggesting. From org-md-separate-elements's docstring:
2. In an item, remove any blank line before the very first
paragraph and the next sub-list.
As a consequence, we try hard to produce
- Foo 2:
- Foo 21
- Foo 22
instead of
- Foo 2:
- Foo 21
- Foo 22
which was the case in early versions of Markdown exporter. I guess we
should produce the latter only when the sub-list is followed by another
block element, e.g., "End of Foo 2 item".
WDYT?
>> Also, what about other block types, e.g., which one is valid:
>>
>> - Foo 1
>> - Foo 2:
>> - Foo 21
>> - Foo 22
>>
>> #+begin_example
>> Some example
>> #+end_example
>>
>> or
>>
>> - Foo 1
>> - Foo 2:
>> - Foo 21
>> - Foo 22
>> #+begin_example
>> Some example
>> #+end_example
>
> I'm not sure to understand what you have in mind: are these last two
> examples at org mode level?
I'm trying to generalize the rule. Your previous suggestion applied to
paragraphs. I wondered if it was the same with other block types, e.g.,
example blocks.
Regards,
