emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: flow <adolflow@sindominio.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: orgmode to markdown
Date: Thu, 04 Jun 2015 00:18:02 +0200	[thread overview]
Message-ID: <877frksag5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1433237666.15774.24.camel@sindominio.net> (flow's message of "Tue, 02 Jun 2015 11:34:26 +0200")

flow <adolflow@sindominio.net> writes:

> I guessed setext support 6 levels so I don't know why ox-md supprot just
> 2 levels although my exporter seems to support 3 levels. Why?

Setext style supports only 2 levels. Atx supports 6 of them, per
<http://daringfireball.net/projects/markdown/syntax#header>.

> That's a good question but not what I wanted to know. What I want -and
> I would like to know whay ox-md doesn't- is to export org as org-mode
> to html does:
>
> - The title becomes h1, so the org title becomes # or ===, I don't mind
> - The * becomes h2, so the org * becomes ## or ----
> - The ** becomes h3, so the org ** becomes ### (in case it supports 3
> leveles)
> - etc.
>
> What do you think about it?

I think it is very opinionated and may be undesirable in the general
case. It means that every headline would be numbered 1.xxx. 

Also some Markdown extensions provide meta-data keywords to specify,
e.g., the title of the document. This behaviour would just get in the
way for them since headlines would get one too many level with no real
reason.

There are several workarounds:

  - you can define filters to add another level to each headline and
    title at the beginning of the document.

  - you can use a {{{title}}} macro, e.g.,

      @@md:#@@ {{{title}}}

    and shift other headlines

If this is common enough, we could also add a defcustom to toggle this
behaviour (yet, off by default). But is it common enough?


Regards,

  reply	other threads:[~2015-06-03 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31  9:36 orgmode to markdown flow
2015-05-31 22:12 ` Nicolas Goaziou
2015-06-02  9:34   ` flow
2015-06-03 22:18     ` Nicolas Goaziou [this message]
2015-06-04  9:54       ` Rasmus
2015-06-04 13:26       ` flow

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=877frksag5.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=adolflow@sindominio.net \
    --cc=emacs-orgmode@gnu.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).