From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH 1/1] filters: generate anchor links from markdown
Date: Sat, 25 Aug 2018 11:11:39 -0600 [thread overview]
Message-ID: <CAHmME9rdjArjZ7qrvbBip2-AuZ9GOktyY5EQOp_Cza_g+cJAtA@mail.gmail.com> (raw)
In-Reply-To: <20180825140237.221dd41a@leda>
The effect is just anchor links, but it doesn't add an actual ToC, right?
next prev parent reply other threads:[~2018-08-25 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 9:56 Table of Contents links using the format #link are not followed actionmystique
2018-07-13 16:14 ` list
2018-07-13 16:39 `
2018-07-13 19:48 ` [PATCH 1/1] filters: generate anchor links from markdown list
2018-08-25 9:45 ` john
2018-08-25 12:02 ` list
2018-08-25 17:11 ` Jason [this message]
2018-08-25 17:47 ` john
2018-08-26 0:01 ` Jason
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9rdjArjZ7qrvbBip2-AuZ9GOktyY5EQOp_Cza_g+cJAtA@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/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.
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 NNTP newsgroup(s).