From: Vin Cent <irakay17-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: What must I do to get any LUA script to work ?
Date: Fri, 1 Oct 2021 06:04:21 -0700 (PDT) [thread overview]
Message-ID: <1ad4d633-8045-4611-97de-63757c38fa9fn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1727 bytes --]
Greetings,
I have been spending time pulling my hair and reducing my code and
ambitions.
Now (based on the BlockCode example from my LUA code is simply reduced to :
function Span(s)
s.identifier = "ggg";
end
I based that on examples I found here
: https://issueexplorer.com/issue/lierdakil/pandoc-crossref/319
and based on the Span description from https://pandoc.org/lua-filters.html
My very obvious expectation is that any generated span element has a "ggg"
identifier.
I don't know how I could define a more trivial function. However, nothing
ever works.
This started with comparisons and real code. Since nothing works, I have
reduced it to this oneliner, which still doesn't.
When I compile my (.tex) code (into epub), this continues producing blocks
such as :
<p><span id="fig:LettreChessCarleyCo"
label="fig:LettreChessCarleyCo">[fig:LettreChessCarleyCo]</span></p>
My compilation is run with this command :
pandoc -L ../pandocLabelFilter.lua -Fpandoc-crossref -o ebook.epub epub.tex
--epub-metadata=metadata.xml --epub-cover-image=IMG/couverture.jpg --toc
--toc-depth=2 --resource-path=IMG/ --default-image-extension=jpg
../pandocLabelFilter.lua contains what I pasted above.
So, what must I do additionnally so that any LUA code accepts to be run for
real ?
Thanks,
Vincent
--
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/1ad4d633-8045-4611-97de-63757c38fa9fn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2570 bytes --]
next reply other threads:[~2021-10-01 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHXtsTdG14zutCcx0m4OHZQ7WOw7qu+HO0////jS4CAACGgwg==>
[not found] ` <AQHXtsTdG14zutCcx0m4OHZQ7WOw7qu+HO0/>
2021-10-01 13:04 ` Vin Cent [this message]
[not found] ` <1ad4d633-8045-4611-97de-63757c38fa9fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-10-01 13:07 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <54c55b4dc2234d6cb0015bb40d8a8ac7-NSENcxR/0n0@public.gmane.org>
2021-10-01 13:24 ` Vin Cent
[not found] ` <0ed66c25-3797-4cf4-986a-92ff787f30cbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-10-01 13:24 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <1178c58675b0461e9f49669ab19d29d2-NSENcxR/0n0@public.gmane.org>
2021-10-01 13:33 ` Vin Cent
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=1ad4d633-8045-4611-97de-63757c38fa9fn@googlegroups.com \
--to=irakay17-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).