From: "Denis Bitouzé" <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Cc: "Denis Bitouzé"
<public-dbitouze-39ZsbGIQGT5GWvitb5QawA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: Re: Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
Date: Wed, 16 Sep 2015 20:03:09 +0200 [thread overview]
Message-ID: <m3oah26y3m.fsf@example.com> (raw)
In-Reply-To: <87h9muwmr8.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> (Nicolas Goaziou's message of "Wed, 16 Sep 2015 14:51:23 +0200")
Le 16/09/15 à 14h51, Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> a écrit :
> Denis Bitouzé <dbitouze-39ZsbGIQGT5GWvitb5QawA-XMD5yJDbdMReXY1tMh2IBg@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?
Indeed but maybe my usecase is too specific for consuming time on it...
>>> 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.
Indeed, this a problem as the Markdown export will put "Some example" on
a separate line as well.
Maybe other more experienced Markdown users could help.
Regards,
--
Denis
prev parent reply other threads:[~2015-09-16 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 14:57 Bug: Extra blank line in subitem list when exported to markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)] Denis Bitouzé
2015-09-13 20:41 ` Nicolas Goaziou
[not found] ` <8737yiuk62.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-14 7:32 ` Denis Bitouzé
2015-09-16 12:51 ` Nicolas Goaziou
[not found] ` <87h9muwmr8.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-16 18:03 ` Denis Bitouzé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3oah26y3m.fsf@example.com \
--to=dbitouze-39zsbgiqgt5gwvitb5qawa@public.gmane.org \
--cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
--cc=public-dbitouze-39ZsbGIQGT5GWvitb5QawA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).