From: Hans Hagen <j.hagen@xs4all.nl>
To: "Ramón Casares" <papa@ramoncasares.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: luametatex segmentation fault
Date: Sun, 12 Jan 2020 14:19:32 +0100 [thread overview]
Message-ID: <6788ac38-5621-ea12-3dce-7c5ec99e4af3@xs4all.nl> (raw)
In-Reply-To: <20200112132331.c5775081140becc587f7f63a@ramoncasares.com>
On 1/12/2020 1:23 PM, Ramón Casares wrote:
> On Sun, 12 Jan 2020 12:00:55 +0100
> Hans Hagen <j.hagen@xs4all.nl> wrote:
>
>> On 1/12/2020 8:22 AM, Ramón Casares wrote:
>>> ~/context/tex/texmf-linux-64/bin/luametatex --ini lmtx.tex
>>
>> so what is that call?
>>
>> luametatex --ini lmtx.tex
>>
>> what in that tex file?
>
> <pre>
> $ cat $(~/context/tex/texmf-linux-64/bin/mtxrun --locate lmtx.tex)
> \input plain
>
> \directlua {tex.enableprimitives('', tex.extraprimitives())}
>
> \pdfoutput=1
you should initialize a couple of file relates callbacks in a lua file
that is then passed as extra argument
but even then, \pdfoutput won't work because there is no backend and
therefore there are no \pdf frontend commands
but if you want to play with plain, you can use a lot of plain commands
in context so best use
lmtx.tex :
\starttext
...
\stoptext
with
context lmtx
unless you want to start with defining a backend and all kind of font
related code
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-01-12 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 14:27 Ramón Casares
2020-01-11 21:14 ` Hans Hagen
2020-01-12 7:22 ` Ramón Casares
2020-01-12 11:00 ` Hans Hagen
2020-01-12 12:23 ` Ramón Casares
2020-01-12 13:19 ` Hans Hagen [this message]
2020-01-12 11:42 ` Hans Hagen
2020-01-12 12:27 ` Ramón Casares
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=6788ac38-5621-ea12-3dce-7c5ec99e4af3@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=papa@ramoncasares.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.
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).