From: K4zuki <k.yamamoto.08136891-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: [ FYI ] testing PANDOC_VERSION == {2,15} doesn't work
Date: Thu, 19 May 2022 05:03:34 -0700 (PDT) [thread overview]
Message-ID: <99207986-698f-4f37-9827-e5ea5b6c40e6n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1275 bytes --]
Hello,
This is a kind of bug report for pandoc==2.15 specific.
I have faced strange behavior of lua filter, which processes Link, with
pandoc==2.15. After some research, I found this is kinda related to issue
#7639 (https://github.com/jgm/pandoc/issues/7639).
So now I am trying to put a message that filter won't work with
pandoc==2.15 when it is so, like following code snippet, but Lua filter (or
Lua subsystem) doesn't detect pandoc's version either.
```lua
if PANDOC_VERSION=={2,15} then
print("this filter wont work with pandoc==2.15")
end
```
The message won't appear with pandoc==2.15. On the other hand,
`tostring(PANDOC_VERSION)` returns "2.15". So if anyone trying to handle
Link with pandoc==2.15, use tostring(PANDOC_VERSION) to filter out pandoc
version.
For your information,
Kazuki Yamamoto / _K4ZUKI_ (https://twitter.com/_K4ZUKI_)
--
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/99207986-698f-4f37-9827-e5ea5b6c40e6n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1738 bytes --]
reply other threads:[~2022-05-19 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=99207986-698f-4f37-9827-e5ea5b6c40e6n@googlegroups.com \
--to=k.yamamoto.08136891-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).