From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: Maxim Nikulin <manikulin@gmail.com>,
Ihor Radchenko <yantar92@gmail.com>,
Matt Huszagh <huszaghmatt@gmail.com>,
"Thomas S. Dye" <tsd@tsdye.online>,
Dominik Schrempf <dominik.schrempf@gmail.com>,
Greg Minshall <minshall@umich.edu>,
orgmode <emacs-orgmode@gnu.org>,
Tim Cross <theophilusx@gmail.com>
Subject: Re: LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX?
Date: Sat, 09 Jul 2022 11:10:29 +0000 [thread overview]
Message-ID: <87k08m8rtm.fsf@posteo.net> (raw)
In-Reply-To: <87czeft1dd.fsf@tsdye.online> (Thomas S. Dye's message of "Fri, 08 Jul 2022 17:23:58 -1000")
Hi Thomas,
Thomas S. Dye writes:
> Yes, what I called Babel you call org-babel. I don't know if the Lua
> handler of source blocks in Org might be useful for someone interested
> to write Lua extensions to LaTeX.
I'm writing a package for LuaLaTeX in Org[1] using lua code blocks, and
everything works fine. But if you mean to evaluate these blocks from
Org, it wouldn't really make sense because LuaTeX uses its own Lua
interpreter and that's where the code should be evaluated. For example,
in LuaTeX you should use tex.print or tex.sprint to print a result in
LaTeX, instead of 'print'.
A simple example to create a counter using Lua:
\newcommand{\mydefcounter}[2]{{\directlua{#1 = #2}}}
\newcommand{\mycounter}[2]{\directlua{%
function count ()
#1 = #1 + #2
tex.print (#1)
end
count()
}}
\mydefcounter{foo}{0}
\mycounter{foo}{1}
\mycounter{foo}{1}
\mycounter{foo}{1}
You might want to take a look at the chickenize package, which includes
loads of examples and is very instructive.
https://www.ctan.org/pkg/chickenize
[1] btw, I thought I was the only one to write a LaTeX package in Org,
instead of the 'official' LaTeX docstrip suite (doing it in Org is
infinitely more comfortable!), but I've seen that the wallcalendar
package has also taken the unorthodox route, with all source code and
documentation in Org :-):
https://github.com/profound-labs/wallcalendar/blob/master/Makefile
Best regards,
Juan Manuel
next prev parent reply other threads:[~2022-07-09 11:14 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 12:17 LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX? Juan Manuel Macías
2022-07-08 15:49 ` Uwe Brauer
2022-07-08 16:46 ` Juan Manuel Macías
2022-07-08 15:54 ` Greg Minshall
2022-07-08 16:13 ` Thomas S. Dye
2022-07-08 17:27 ` Bruce D'Arcus
2022-07-08 19:03 ` Juan Manuel Macías
2022-07-08 18:49 ` Thomas S. Dye
2022-07-09 2:23 ` Max Nikulin
2022-07-09 3:23 ` Thomas S. Dye
2022-07-09 11:10 ` Juan Manuel Macías [this message]
2022-07-09 3:24 ` Tim Cross
2022-07-09 3:50 ` Ihor Radchenko
2022-07-09 4:10 ` Tim Cross
2022-07-09 5:35 ` Dominik Schrempf
2022-07-09 6:31 ` Max Nikulin
2022-07-09 9:59 ` Juan Manuel Macías
2022-07-09 23:49 ` Tim Cross
2022-07-10 11:19 ` M-x org-create-worg-article command? (was: LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX?) Ihor Radchenko
2022-07-10 19:06 ` Tim Cross
2022-07-11 2:09 ` Ihor Radchenko
2022-07-11 2:49 ` Tim Cross
2022-07-11 3:18 ` Ihor Radchenko
2022-07-11 4:00 ` Tim Cross
2022-07-11 4:20 ` Ihor Radchenko
2022-07-10 19:31 ` LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX? Juan Manuel Macías
2022-07-09 10:42 ` Juan Manuel Macías
2022-07-09 12:15 ` Max Nikulin
2022-07-09 14:58 ` Juan Manuel Macías
[not found] ` <b58ee3cc-c58c-b627-9cc5-51993020db2c@gmail.com>
2022-07-09 20:22 ` Juan Manuel Macías
2022-07-10 20:23 ` [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...") Juan Manuel Macías
2022-07-10 20:31 ` Juan Manuel Macías
2022-07-10 20:58 ` Tim Cross
2022-07-11 13:34 ` Juan Manuel Macías
2022-07-11 2:19 ` Ihor Radchenko
2022-07-11 7:50 ` Stefan Nobis
2022-07-11 14:19 ` Timothy
2022-07-11 15:00 ` Juan Manuel Macías
2022-07-11 17:45 ` fontsets (was: [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...")) Timothy
2022-07-11 22:09 ` fontsets Juan Manuel Macías
2022-07-12 7:12 ` fontsets Stefan Nobis
2022-07-12 11:37 ` fontsets Juan Manuel Macías
2022-07-12 15:26 ` Fallback fonts in LuaTeX via 'luaotfload.add_fallback' (was "Fontsets") Juan Manuel Macías
2022-07-15 14:35 ` Max Nikulin
2022-07-11 3:59 ` [possible patch] Basic fontspec code for LuaLaTeX and XelaTeX (was "LaTeX export: when is it more useful...") Greg Minshall
2022-07-11 8:05 ` Stefan Nobis
2022-07-11 11:39 ` Juan Manuel Macías
2022-07-11 12:04 ` Juan Manuel Macías
2022-07-11 12:31 ` Max Nikulin
2022-07-11 14:23 ` Juan Manuel Macías
2022-07-11 17:20 ` Max Nikulin
2022-07-16 3:01 ` Max Nikulin
2022-07-11 17:08 ` LaTeX export: when is it more useful to use LuaTeX instead of pdfTeX? Max Nikulin
2022-07-10 2:12 ` Max Nikulin
2022-07-09 0:34 ` Matt Huszagh
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k08m8rtm.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=dominik.schrempf@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=huszaghmatt@gmail.com \
--cc=manikulin@gmail.com \
--cc=minshall@umich.edu \
--cc=theophilusx@gmail.com \
--cc=tsd@tsdye.online \
--cc=yantar92@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).