From: Shir <shirdekel94-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: `auto_identifiers` causing duplicate identifiers
Date: Sun, 23 May 2021 23:57:15 -0700 (PDT) [thread overview]
Message-ID: <099f0289-7ff2-4f84-b983-8af49f257915n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]
I have a `test.md` that looks like this:
```
# test
# test {#test}
```
I ran `pandoc test.md --to latex --from markdown` and expected to get the
following:
```
\hypertarget{test}{%
\section{test}\label{test-1}}
\hypertarget{test}{%
\section{test}\label{test}}
```
Instead, I got:
```
[WARNING] Duplicate identifier 'test' at line 6 column 1
\hypertarget{test}{%
\section{test}\label{test}}
\hypertarget{test}{%
\section{test}\label{test}}
```
Turning `auto_identifiers` off "fixes" this by not giving the first
instance a label. But shouldn't `auto_identifiers` be able to automatically
label headings while taking into account existing IDs?
--
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/099f0289-7ff2-4f84-b983-8af49f257915n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1623 bytes --]
next reply other threads:[~2021-05-24 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 6:57 Shir [this message]
[not found] ` <099f0289-7ff2-4f84-b983-8af49f257915n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-24 18:32 ` John MacFarlane
[not found] ` <m21r9woudj.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-25 1:00 ` Shir
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=099f0289-7ff2-4f84-b983-8af49f257915n@googlegroups.com \
--to=shirdekel94-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).