From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Andrew Mercer
<mercergeoinfo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: citeproc citation not found
Date: Tue, 15 Dec 2020 08:57:58 -0800 [thread overview]
Message-ID: <m2k0tjxazt.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <aeffb619-6913-4d05-a293-c93656df0fecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Are you sure there isn't a `nocite` in your external yaml file?
When you use pandoc to produce a YAML bibliography, e.g. from
a bibtex source
pandoc -t markdown -s mybib.bib
it will insert a `nocite: "[@*]"` in the bibliography, which
will cause all items to be cited. Just remove that line.
Andrew Mercer <mercergeoinfo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Can confirm that this problem occurs when using pandoc 2.11.2 on Ubuntu.
> The workaround is the same; use yaml references in header, not in external
> file.
>
> On Tuesday, 8 December 2020 at 09:47:09 UTC+1 Andrew Mercer wrote:
>
>> Sorry for the late reply, I thought I had replied to this already.
>> I have not place a nocite anywhere in the md file.
>> This really seems like a wandering bug. I cant say whether 2.11.1 placed
>> all references in the reference list as I didn't test that but it certainly
>> happens when using 2.11.2
>> What I find very confusing is the fact that pandoc can create a yaml or
>> json from a bib file but can't use external references when compiling a
>> document. All of these files are in the same directory, the mad, bib, json
>> and yaml.
>> Perhaps the fact that pandoc couldn't find my latex template, which also
>> resides in the same directory, indicates a common issue. Somehow the path
>> is corrupted when compiling a markdown file that calls on secondary files.
>>
>> On Tuesday, 1 December 2020 at 19:39:21 UTC+1 John MacFarlane wrote:
>>
>>> Andrew Mercer <mercer...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>
>>> > Further update. Adding references to the yaml works but ALL references
>>> in
>>> > the yaml are then place in the reference list at the end of the
>>> compiled
>>> > document.
>>>
>>> Do you have `nocite` in your metadata?
>>>
>>>
>
> --
> 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/aeffb619-6913-4d05-a293-c93656df0fecn%40googlegroups.com.
next prev parent reply other threads:[~2020-12-15 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 17:45 Andrew Mercer
[not found] ` <c5fad0e6-186d-4e31-8b38-063e12ff5547n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-18 19:53 ` Pranesh Prakash
[not found] ` <3e0b4d78-7fa0-49a1-9aec-76f0f35a68dbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-01 13:31 ` Andrew Mercer
[not found] ` <b1de277e-6993-49ff-80be-34161ed23c18n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-01 14:01 ` Andrew Mercer
[not found] ` <0a64670e-a33d-4f2d-8e79-4e03bda6ffc6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-01 15:06 ` Andrew Mercer
[not found] ` <26044863-4227-481e-bf49-598d385ba76fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-01 18:39 ` John MacFarlane
[not found] ` <m2im9lxtfb.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-12-08 8:47 ` Andrew Mercer
[not found] ` <ac9eac16-5dab-4879-a5d7-03ab39e95953n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-15 15:16 ` Andrew Mercer
[not found] ` <aeffb619-6913-4d05-a293-c93656df0fecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-15 16:57 ` John MacFarlane [this message]
2020-12-01 15:09 ` Pranesh Prakash
[not found] ` <d99b3932-8d94-4112-b5eb-3bb04bceeaaen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-01 17:22 ` Pranesh Prakash
2020-12-01 18:37 ` John MacFarlane
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=m2k0tjxazt.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=mercergeoinfo-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).