From: Hans Hagen <j.hagen@xs4all.nl>
To: Vladimir Lomov <lomov.vl@yandex.ru>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context (lmtx) segfaults on x86_64 linux
Date: Wed, 11 Sep 2019 11:40:51 +0200 [thread overview]
Message-ID: <a6f4512c-2592-759f-1334-3b79c8e2ab62@xs4all.nl> (raw)
In-Reply-To: <20190911090226.GF844@smoon.vl-lomov.ru>
On 9/11/2019 11:02 AM, Vladimir Lomov wrote:
>>> │ ├── cont-en.lui
>>> │ └── cont-en.luv
>>
>> these are regular lua files
>
> The last two, Ok.
Indeed. These are startup related files.
> That make sense, lua, (lub), luc, lud but even lua files are different
> or do you mean that luc/lud are generated (compiled) from lua and then
> contex don't read them only luc/lud?
The lua files are probably not that different but indeed the other ones
are bytecode files and normally read (with the lua files as fallbacks in
case of a failure) which is more efficient (a =lua, c = luatex bytecode
(5.3), b = luajit bytecode (hybrid 5.1 / 5.2), d = luametatex bytecode
(5.4). At some point the jit variant might be dropped and in the long
run we might only have luametatex.
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:[~2019-09-11 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 14:11 Vladimir Lomov
2019-09-10 15:18 ` Hans Hagen
2019-09-10 15:50 ` Aditya Mahajan
2019-09-10 23:19 ` Henri Menke
2019-09-11 1:41 ` Vladimir Lomov
2019-09-11 6:39 ` Hans Hagen
2019-09-11 8:14 ` Vladimir Lomov
2019-09-11 8:38 ` Hans Hagen
2019-09-11 8:51 ` Vladimir Lomov
2019-09-11 8:54 ` Hans Hagen
2019-09-11 9:02 ` Vladimir Lomov
2019-09-11 9:40 ` Hans Hagen [this message]
2019-09-11 7:03 ` Hans Hagen
2019-09-11 1:06 ` Vladimir Lomov
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=a6f4512c-2592-759f-1334-3b79c8e2ab62@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=lomov.vl@yandex.ru \
--cc=ntg-context@ntg.nl \
/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).