From: Psionic K <psionik@positron.solutions>
To: emacs-orgmode@gnu.org
Subject: Keyword TOC generation for GFM
Date: Sun, 24 Nov 2024 20:03:02 +0900 [thread overview]
Message-ID: <CADQMGATox-a-0gNwpBroinpsKYFqX+KmBvLTtg=mAA7PT4UXzA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Reportedly, ox-md is somehow responsible for ox-gfm generating a TOC with
anchors. Don't quote me on that. I don't believe it either.
Facts I actually believe: ox-gfm will generate a github flavor table if I
just set `toc' to `t' at the top of my readme. However, if I try to create
a partial TOC, as I have done with dslide, the normal ox-md behavior
returns and I get vanilla markdown links.
First report on ox-gfm: https://github.com/larstvei/ox-gfm/issues/51
You can see my toc settings here:
https://raw.githubusercontent.com/positron-solutions/dslide/refs/heads/master/doc/README.org
This is the line I'm using to generate a TOC at a specific point in the
document:
#+toc: headlines 2
What I'm looking for is vague understanding of where the problem might
actually be and what pieces of code the solution might touch. I haven't
touched org's exporters much and don't know where to start.
[-- Attachment #2: Type: text/html, Size: 1204 bytes --]
reply other threads:[~2024-11-24 11:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CADQMGATox-a-0gNwpBroinpsKYFqX+KmBvLTtg=mAA7PT4UXzA@mail.gmail.com' \
--to=psionik@positron.solutions \
--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).