From: Jean-Christophe Helary <lists@traduction-libre.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Protesilaos Stavrou <info@protesilaos.com>,
emacs-humanities@gnu.org, orgmode <emacs-orgmode@gnu.org>
Subject: Re: Elegant way to export org to Markdown ?
Date: Sat, 2 Oct 2021 15:32:27 +0900 [thread overview]
Message-ID: <FB2EB7EF-710D-4F1D-B745-BB30B15B63FD@traduction-libre.org> (raw)
In-Reply-To: <87y27cx7ue.fsf@localhost>
> On Oct 2, 2021, at 15:24, Ihor Radchenko <yantar92@gmail.com> wrote:
>
> Jean-Christophe Helary <lists@traduction-libre.org> writes:
>
>> My follow-up question is, most of the ox-stuff seem to be installed by default, as far as I can tell. Why is ox-md not ?
>
> Not most. The default export backends are:
>
>> org-export-backends is a variable defined in org.el.
>>
>> Value
>> (ascii html icalendar latex odt)
>
> You can also customise this variable instead of direct (require 'ox-md)
>
> Why not all backends are loaded? Mostly to reduce Org loading speed that
> some people complain about.
Also, I could have checked the manual... It was all there... Apologies for the noise.
Next (related) question:
Why that ugly number in front of headers defined with <hn> in HTML ?
--
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
next prev parent reply other threads:[~2021-10-02 6:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 5:20 Elegant way to export org to Markdown ? Jean-Christophe Helary
2021-10-02 5:55 ` Ihor Radchenko
2021-10-02 5:57 ` Protesilaos Stavrou
2021-10-02 6:10 ` Jean-Christophe Helary
2021-10-02 6:24 ` Ihor Radchenko
2021-10-02 6:32 ` Jean-Christophe Helary [this message]
2021-10-02 7:00 ` Ihor Radchenko
2021-10-02 7:34 ` Jean-Christophe Helary
2021-10-02 7:44 ` Tim Cross
2021-10-02 9:10 ` Jean-Christophe Helary
2021-10-02 12:18 ` Morgan Willcock
2021-10-02 13:31 ` Jean-Christophe Helary
2021-10-03 4:11 ` [emacs-humanities] " Jean-Christophe Helary
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=FB2EB7EF-710D-4F1D-B745-BB30B15B63FD@traduction-libre.org \
--to=lists@traduction-libre.org \
--cc=emacs-humanities@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=info@protesilaos.com \
--cc=yantar92@gmail.com \
/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).