From: Ihor Radchenko <yantar92@posteo.net>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: org mode to github markdown
Date: Sun, 07 May 2023 19:45:36 +0000 [thread overview]
Message-ID: <87zg6ggc2n.fsf@localhost> (raw)
In-Reply-To: <8373262A-9972-4F6F-9801-50271061D4A8@norang.ca>
Bernt Hansen <bernt@norang.ca> writes:
> (who has been away from the org-mode mailing list for way too many years...)
Welcome back. Your GTD config got me started with Org years back :)
> I'm not sure I fully understand your question.
> You are looking for an org-mode export to markdown? Isn't that already included in recent org versions?
>
> C-c C-e C-s m M
Markdown is not a single standard. There are several variations of the
syntax. See https://en.wikipedia.org/wiki/Markdown
We support the most basic "vanilla" markdown in ox-md.el. But Github
uses its own flavour, which we do not export to. In particular, vanilla
markdown allow direct HTML fragments, which are disabled in
GitHub/Reddit/many other websites for security reasons. Instead, they
invent new markdown constructs that are explicitly supported. But there
are numerous Markdown syntax extensions - it is hard to support them
unless we have a dedicated maintainer.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-05-07 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 17:51 org mode to github markdown Bernt Hansen
2023-05-07 19:45 ` Ihor Radchenko [this message]
2023-05-08 2:06 ` Max Nikulin
2023-05-08 12:28 ` Uwe Brauer
-- strict thread matches above, loose matches on Subject: below --
2023-05-07 17:25 Uwe Brauer
2023-05-07 19:58 ` Ihor Radchenko
2023-05-07 19:59 ` Uwe Brauer
2023-05-08 3:14 ` Ruijie Yu via General discussions about Org-mode.
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=87zg6ggc2n.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bernt@norang.ca \
--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).