public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "andreas....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <andreas.schamanek-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: All numeric heading identifiers
Date: Sun, 29 Aug 2021 10:49:29 -0700 (PDT)	[thread overview]
Message-ID: <70061a93-5913-4668-8bac-3bdaedb9c710n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1037 bytes --]

I read the sections Heading Identifiers and Extension: auto_identifiers 
<https://pandoc.org/MANUAL.html#extension-auto_identifiers> in the manual. 
So, I think I understand why the following produces `id="section"`

$ printf '# 47\n' | pandoc
<h1 id="section">47</h1>

But why is it that I cannot make Pandoc use a specific identifier like in

$ printf '# 47 {#47}\n' | pandoc 
<h1 id="section">47 {#47}</h1>

I expected Pandoc to produce `id="47"`.

BTW, I came upon this because I was wondering how to reference ISO dates in 
headers, like

## 2021-08-29

because

## 2021-08-29 {#2021-08-29}

produces `id="section"` too.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/70061a93-5913-4668-8bac-3bdaedb9c710n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1890 bytes --]

             reply	other threads:[~2021-08-29 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 17:49 andreas....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [not found] ` <70061a93-5913-4668-8bac-3bdaedb9c710n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-29 17:56   ` 'Saku Laesvuori' via pandoc-discuss
     [not found]     ` <20210829175628.5vqzpwmdgtcht6h7-8gZB9jwuPzi3bl2xfHZzInzaFgp7qdfK@public.gmane.org>
2021-08-29 18:21       ` William Lupton
2021-08-30  2:06   ` John MacFarlane
     [not found]     ` <m2lf4jbs9x.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-08-30  5:29       ` andreas....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

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=70061a93-5913-4668-8bac-3bdaedb9c710n@googlegroups.com \
    --to=andreas.schamanek-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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).