public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "nisze...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<niszet0016-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How do we get version of citeproc?
Date: Sun, 18 Oct 2020 22:13:03 -0700	[thread overview]
Message-ID: <m2imb66bog.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <c24e8eae-edfe-47fe-9792-fdfe92c5dbd9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


pandoc 2.11.0.2 is compiled against the most recent release
of citeproc.  But you're right, it would be good to report
this along with the other verisons  we report with --version.
I'll make that change.

"nisze...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <niszet0016-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> From Pandoc 2.11, pandoc-citeproc is replaced to built-in citeproc.
> But now, I cannot get the version of it. It should be shown when the user 
> check the pandoc version as follows, I think. Currently other libs are 
> shown their versions.
>
> ```
>> pandoc -v
> pandoc 2.11.0.2
> Compiled with pandoc-types 1.22, texmath 0.12.0.3, skylighting 0.10.0.2
> ```
>
> I would like to check that for debugging (or reporting). Is there any other 
> option to get the version of citeproc?
>
> Thanks,
> niszet
>
> -- 
> 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/c24e8eae-edfe-47fe-9792-fdfe92c5dbd9n%40googlegroups.com.


  parent reply	other threads:[~2020-10-19  5:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18  1:58 nisze...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found] ` <c24e8eae-edfe-47fe-9792-fdfe92c5dbd9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-10-19  5:13   ` John MacFarlane [this message]
     [not found]     ` <m2imb66bog.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-10-20 13:40       ` nisze...-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=m2imb66bog.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=niszet0016-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).