[email protected] writes: >> 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
Sorry, I do not quite understand what that video is trying to show. Also, I feel like you missed my question about differences between vanilla markdown and commonmark. I far as I understand, commonmark does add a couple of features compared to vanilla markdown (like \ at the end of line, allowing paragraphs to start right after lists, new list bullets, etc), but from practical point of view we can simply retain the vanilla syntax (we generate it anyway) and *only* add ```lang fenced blocks that simply cannot be represented using vanilla syntax (it has no way to specify language name). Please correct me if I am wrong. > 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 > --- I am confused. You were proposing to add commonmark exporter. How does haunt have anything to do with it? (I do understand that your personal goal is compatibility with your static site generator of choice, but from Org mode project perspective, it is irrelevant. Only supporting Commonmark is) > 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 Ok. I do see ```language being defined in https://spec.commonmark.org/0.31.2/#info-string > 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. AFAIK, commonmark has no notion of table of contents. Could you please explain in text what is wrong with TOC generated by ox-md? > 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. Let me make it clear. I see no reason for _Org mode_ to support haunt specifically. Only commonmark. So, I would welcome contributions to add commonmark support (possibly with some defaults compatible with haunt), but I see no reason to add things specific to haunt that cannot be reused elsewhere. -- Ihor Radchenko // yantar92, Org mode maintainer, 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>
