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: Fri, 11 Dec 2020 10:53:27 -0500 [thread overview]
Message-ID: <3b1809bdd1a087709c7d91c3c8d492cb@isnotmyreal.name> (raw)
In-Reply-To: <9aa624fff553d9d140a6d89aab12e21b@isnotmyreal.name>
An update!
I am very pleased to announce, that my campaign took me only a little
less than 2 weeks to achieve success! :)
And so, from now on, not only myself but /everyone/ who prefer writing
in .org instead of .md now have a clear path to nice looking rendered
HTML which is on par with the default .md at Sourcehut![0]
This was the only real gripe I had with that platform, as I generally
love what Drew is trying to do over there and I really wanted to
continue my support and participation. And now I can!
The main issue was that in-page links, generated by exporting .org ->
.md, and then getting processed by Sourcehut's HTML renderer were
getting broken in the process. However now they are working, as can now
be seen for example at README of one of my projects:
https://sr.ht/~trs-80/rofi-in-elisp/
Please feel free to go there and click in-page links! In fact I cannot
remember the last time I got so much enjoyment from something so simple
as clicking on a working in-page link! :D
Just to re-cap, I had taken a 2 pronged approach. First was on sr.ht
mailing list[1] about trying to fix the id sanitation in anchor links.
After some discussion and a couple patches, this approach is now live
and working.
However, simultaneously, I had also been pursuing a Pandoc based
solution (which, amazingly, was /also/ broken, but for a different
reason). This second approach has now also bourne fruit in the form of
a patch and a workaround, and eventually should also become fully
supported.[2]
I include both here for the benefit of anyone who comes searching along
later.
Special thanks to Tim Cross for helping me get the exact issue nailed
down in my head so I could go forth onto other mailing lists and fora
and explain the issue with clarity.
It really feels great to make some small contribution back to the larger
Orgmode ecosystem which has given me so much.
Cheers,
TRS-80
[0] https://sourcehut.org
[1]
https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3Cfe7aa296-9c90-463d-b4e6-50eeb7e57428%40localhost%3E
[2] https://github.com/jgm/pandoc/issues/6916
prev parent reply other threads:[~2020-12-11 16:05 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
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 [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=3b1809bdd1a087709c7d91c3c8d492cb@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).