November 3, 2025 at 3:44 PM, "Ihor Radchenko" <[email protected] mailto:[email protected]?to=%22Ihor%20Radchenko%22%20%3Cyantar92%40posteo.net%3E > wrote:
> > [email protected] mailto:[email protected] writes: > > > > > > > > > That said, your links are to private repository, so I have no idea about > > > the actual code you are talking about. > > > > > That is my mistake: > > > > https://git.sr.ht/~gnucode/ox-commonmark > > > Looking at the code, I can see that you mostly introduced the ``` > syntax. You also added a more appropriate template, but that one does > not appear to have anything to do with commonmark per se. > > Could you please summarize the main differences between vanilla markdown > and commonmark markups? I made a short video showing why I made ox-commonmark.el. https://video.hardlimit.com/w/pMS4e6P4kAsZgpnhrtaJjr As I started making it, I realized that perhaps ox-md.el is actually SUPER close to working with haunt. The main differences are: 1) Haunt commmonmark files must begin with something like this: title: Updating TalosII's firmware date: 2025-10-25 17:00 author: Joshua Branson summary: My friend's TalosII computer's firmware is using the older versions. Let's update it. tags: talosII raptorcomputing --- 2) Like you mentioned "```sh", "```C", "```scheme", tells haunt to treat certain sections as code. Haunt can then syntax highlight those code regions. I have not yet set this up in my website, but David Thompson has in his blog: https://dthompson.us/projects/haunt.html 3) The way that org-markdown generates the table of contents does not work with haunt. The links do not take you to the sections. I would like to make ox-commonmark.el generate the a TOC with working links. 4) Haunt stores its blog posts in $haunt-blog/posts/ directory. Those files can be texinfo, scribe, markdown, or sxml formats. If you store an org file in there, then haunt build will not work. I'll check with David Thompson, and see if haunt has a feature to ignore org files. That's why I made the org-cm-export-file-to-haunt-dir function. It just exports the file in $haunt-blog/posts-org to $haunt-blog/posts/ . Those are the differances. In short, I just want to make it possible for the casual Emacs user to use org-mode & haunt. If ox-commonmark.el is too simple to be included in org-mode at the point. I could ask David Thompson if we can include it in $haunt-src/etc/ox-commonmark.el for a few release cycles. That might not be a bad idea to get some feedback from haunt users before it gets included in org-mode. Thanks, Joshua > -- > Ihor Radchenko // yantar92, > Org mode maintainer, > Learn more about Org mode at <https://orgmode.org/> https://orgmode.org/%3E . > Support Org development at <https://liberapay.com/org-mode>, > https://liberapay.com/org-mode%3E, > or support my work at <https://liberapay.com/yantar92> > https://liberapay.com/yantar92%3E >
