From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: AW: compiling lpeg into pandoc
Date: Tue, 2 Nov 2021 13:28:15 +0000 [thread overview]
Message-ID: <a4454aeb346b404ba248ee962bacd7cd@unibe.ch> (raw)
In-Reply-To: <878ry67p0o.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
The installed lua version is already 5.4.x Ist that a problem?
________________________________________
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> im Auftrag von Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
Gesendet: Dienstag, 2. November 2021 12:52:55
An: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Betreff: Re: AW: compiling lpeg into pandoc
denis.maier-NSENcxR/0n0@public.gmane.org writes:
> Anyway, so if I install modules via luarocks they become usable in
> filters? (That is, pandoc's lua will find those modules?)
The locations in which Lua searches for libraries are controlled via the
LUA_PATH and LUA_CPATH environment variables. There is a convenient
`luarocks path` command which shows the necessary settings and can be
used to set them:
eval "$(luarocks path)"
After that, the Lua interpreter in pandoc should be able to find all
modules installed via luarocks. Just make sure that luarocks uses
Lua 5.3, which is the version included in pandoc.
--
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/878ry67p0o.fsf%40zeitkraut.de.
next prev parent reply other threads:[~2021-11-02 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 13:38 RFC: " Albert Krewinkel
[not found] ` <87ee806loe.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-11-01 22:06 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <83dbc2c6dcbe49e49e00dac40b73eb65-NSENcxR/0n0@public.gmane.org>
2021-11-02 11:44 ` denis.maier-NSENcxR/0n0
[not found] ` <ec915ee445b6471fb1f252d98a727e3d-NSENcxR/0n0@public.gmane.org>
2021-11-02 11:52 ` Albert Krewinkel
[not found] ` <878ry67p0o.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2021-11-02 12:38 ` BPJ
2021-11-02 13:28 ` denis.maier-NSENcxR/0n0 [this message]
[not found] ` <a4454aeb346b404ba248ee962bacd7cd-NSENcxR/0n0@public.gmane.org>
2021-11-02 13:37 ` BPJ
[not found] ` <CADAJKhD=XdoUF6cg06uNqdGRXW1tdOzidv82=m84n9gSHR-LjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-11-03 9:41 ` krulis....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2021-11-01 23:14 ` RFC: " BPJ
2021-11-08 15:38 ` Albert Krewinkel
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=a4454aeb346b404ba248ee962bacd7cd@unibe.ch \
--to=denis.maier-nsencxr/0n0@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).