From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec?
Date: Wed, 02 Dec 2020 14:56:20 -0500 [thread overview]
Message-ID: <dd8bd5e4345d236caa3fa005e36f01f2@isnotmyreal.name> (raw)
In-Reply-To: <X8fnGuM03gGpiHOj@protected.rcdrun.com>
On 2020-12-02 14:12, Jean Louis wrote:
> Try using pandoc Org to Markdown as that could help until Org
> exporting start working how it should.
Great minds must think alike! :) I tried that already but in-page
links
which look like:
```
[[*Setup][Setup]]
```
Somehow get exported to:
```
*Setup*
```
...which is not a link at all, but rather just italicised text.
In fact, I think I will go now and bring that up to pandoc project...
They have several different flavored Markdown exporters available, I
tried all of them in fact.
FWIW, I also tried going the route of exporting to HTML (which is also
supported at Sourcehut)[0] however I ran into lots of other similar
issues like in OP, as the HTML exporter does the same things with id in
links.
I actually worked on this all day yesterday, still without success. I
am of course still open to any suggestions, but I came to conclusion so
far that fixing the ox-md exporter might be the Right Way and I was
willing to dig into that further, myself.
I work extensively in Orgmode and have plans to publish many more things
(likely on Sourcehut) and I would rather do whatever work is required to
fix ox-md than change all my existing (or new) work to Markdown. I
really do hate Markdown that much. :D
Also, maybe in the meantime I could simply hard code a ToC, but that
still will not fix other in-page links throughout the page (like the
*Setup example, above).
Cheers,
TRS-80
[0] https://man.sr.ht/git.sr.ht/#setting-a-custom-readme
next prev parent reply other threads:[~2020-12-02 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 18:52 Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec? TRS-80
2020-12-02 19:12 ` Jean Louis
2020-12-02 19:56 ` TRS-80 [this message]
2020-12-02 21:32 ` TRS-80
2020-12-02 19:44 ` Tim Cross
2020-12-02 20:44 ` TRS-80
2020-12-02 21:59 ` Tim Cross
2020-12-02 23:17 ` TRS-80
2020-12-02 23:36 ` Tim Cross
2020-12-02 19:45 ` Diego Zamboni
2020-12-02 20:25 ` TRS-80
2020-12-11 15:53 ` TRS-80
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=dd8bd5e4345d236caa3fa005e36f01f2@isnotmyreal.name \
--to=lists.trs-80@isnotmyreal.name \
--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).