From: "Gisbert W. Selke" <gisbert.selke-f2bn9DS6+XnCNGIDtd5pJw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Problem running Lua filters after Pandoc update
Date: Thu, 27 Jan 2022 09:49:32 -0800 (PST) [thread overview]
Message-ID: <6fce8984-db47-468d-9679-591f31815c99n@googlegroups.com> (raw)
In-Reply-To: <87tudpm62b.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1991 bytes --]
That is perfectly what I needed to know, Albert (not to mention that it was
ultra-fast)! In the case of pandoc-quotes, I'll point the author to this
(and supply the fix). In the case of my own scripts, this will teach the
author not to use undocumented interfaces ;-)
Thnxalot -- viele Grüße --
\Gisbert
Albert Krewinkel schrieb am Donnerstag, 27. Januar 2022 um 18:39:33 UTC+1:
> Hi Gisbert,
>
> "Gisbert W. Selke" <gisber...-f2bn9DS6+XnCNGIDtd5pJw@public.gmane.org> writes:
>
> > After updating from Pandoc 2.12.x to 2.17.0.1 some (all?) of my Lua
> > filters stopped working.
>
> I think there's a mixture of reasons here. We have made quite
> substantial changes to the Lua subsystem over the last few
> releases, but *most* of these were backwards compatible when
> looking just at the official API. E.g., while `.c` no longer works
> the way it used to, accessing that field was never really
> supported in the first place. The majority of filters that use
> just the documented API should continue to work.
>
> One change that's not backwards compatible concerns metadata
> tagging: metadata values no longer have a `.t` field. I
> believe most filter authors have updated their filters by now, so
> it may be enough to download newer versions of the broken filters.
> If that doesn't fix it, tell the author about it.
>
> Is this the kind of information you were looking for and does it
> answer your question?
>
> Cheers,
> Albert
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
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/6fce8984-db47-468d-9679-591f31815c99n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2680 bytes --]
prev parent reply other threads:[~2022-01-27 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 16:28 Gisbert W. Selke
[not found] ` <a9a414f3-9400-4a35-bb51-588b2bdcf460n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-27 17:19 ` Albert Krewinkel
[not found] ` <87tudpm62b.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-01-27 17:49 ` Gisbert W. Selke [this message]
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=6fce8984-db47-468d-9679-591f31815c99n@googlegroups.com \
--to=gisbert.selke-f2bn9ds6+xncngidtd5pjw@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).