From: Norman Ramsey <fellswalker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: luacheck configuration for pandoc Lua filters?
Date: Wed, 12 May 2021 11:36:07 -0700 (PDT) [thread overview]
Message-ID: <c4190975-7e98-446a-94a3-9f3df0e344b4n@googlegroups.com> (raw)
In-Reply-To: <CADAJKhDRBLYw8E-J_8DWjcZsfYRuOiF24=dSbcEtXyLmrTkX8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2009 bytes --]
luacheck works with one module at a time, so all I need to do is figure out
the _names_ of the callable objects. I could poke at metatables or could
assume conservatively that all objects are callable. What I don't know how
to do is find callable names that _aren't_ materialized in the `pandoc`
table but are available only via an `__index` metamethod.
On Tuesday, May 11, 2021 at 4:21:47 AM UTC-4 BP wrote:
> Den tis 11 maj 2021 01:16Norman Ramsey <fells...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>
>> I've recently discovered `luacheck`, a fantastic static-analysis tool for
>> Lua programs. I'd like to use it with my Pandoc filters, but it needs a
>> configuration to tell it what functions in the global `pandoc` table are OK
>> to call. If anybody happens to have made such a configuration, please let
>> us know.
>
>
> I guess the fact that most of the constructors in the pandoc library are
> actually callable objects rather than functions may be a problem one way or
> another.
>
>
>> --
>> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/7fd5e3eb-99cd-4bce-84c4-313077e96637n%40googlegroups.com
>> <https://groups.google.com/d/msgid/pandoc-discuss/7fd5e3eb-99cd-4bce-84c4-313077e96637n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
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/c4190975-7e98-446a-94a3-9f3df0e344b4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3427 bytes --]
next prev parent reply other threads:[~2021-05-12 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 23:16 Norman Ramsey
[not found] ` <7fd5e3eb-99cd-4bce-84c4-313077e96637n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-11 8:21 ` BPJ
[not found] ` <CADAJKhDRBLYw8E-J_8DWjcZsfYRuOiF24=dSbcEtXyLmrTkX8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-05-12 18:36 ` Norman Ramsey [this message]
[not found] ` <c4190975-7e98-446a-94a3-9f3df0e344b4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-13 7:46 ` Albert Krewinkel
[not found] ` <87mtszyt2e.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-05-13 17:03 ` Norman Ramsey
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=c4190975-7e98-446a-94a3-9f3df0e344b4n@googlegroups.com \
--to=fellswalker-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).