From: Vladimir Lomov <lomov.vl@yandex.ru>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context (lmtx) segfaults on x86_64 linux
Date: Wed, 11 Sep 2019 17:02:26 +0800 [thread overview]
Message-ID: <20190911090226.GF844@smoon.vl-lomov.ru> (raw)
In-Reply-To: <06794b6e-5164-1c9c-48e2-b63968762433@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2484 bytes --]
Hello
** Hans Hagen [2019-09-11 10:54:41 +0200]:
> On 9/11/2019 10:14 AM, Vladimir Lomov wrote:
>
>> LUAMETATEX:
>>
>> -------------------------------------- 8< --------------------------------------
>> tree $TEXMFCACHE/ | sed -e "s@$HOME/.cache/@@"
>> lmtx/
>> └── luatex-cache
>> └── context
>> └── 5fe67e0bfe781ce0dde776fb1556f32e
>> ├── formats
>> │ └── luametatex
>> │ ├── cont-en.fmt
>> │ ├── cont-en.log
>> │ ├── cont-en.lui
>> │ └── cont-en.luv
>
> these are regular lua files
The last two, Ok.
>
>> └── trees
>> ├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.lua
>> ├── 3952aa25b6a1b9f9f8d3eeb6e65f0039.luc
>> ├── 3f406286dc3075cdfb044f836920f46a.lua
>> ├── 3f406286dc3075cdfb044f836920f46a.luc
>> ├── 3f6978edf9feb817ad6c1f21fc262031.lua
>> ├── 3f6978edf9feb817ad6c1f21fc262031.luc
>> ├── 71c82419867f9a0df8a150196c03c86f.lua
>> ├── 71c82419867f9a0df8a150196c03c86f.luc
>> ├── 73630a261795d9c53610a28af4550cbc.lua
>> ├── 73630a261795d9c53610a28af4550cbc.luc
>> ├── dcb651482955ac31eaab7723b70e0184.lua
>> ├── dcb651482955ac31eaab7723b70e0184.luc
>> ├── fb39a92c95ceca857c3f2d0ee48a2ad3.lua
>> └── fb39a92c95ceca857c3f2d0ee48a2ad3.luc
> actually these *.luc files should be *.lud files so I need to check that
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?
>
> 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
> -----------------------------------------------------------------
---
WBR, Vladimir Lomov
--
Besides, REAL computers have a rename() system call. :-)
-- Larry Wall in <7937@jpl-devvax.JPL.NASA.GOV>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:02 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 [this message]
2019-09-11 9:40 ` Hans Hagen
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=20190911090226.GF844@smoon.vl-lomov.ru \
--to=lomov.vl@yandex.ru \
--cc=j.hagen@xs4all.nl \
--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).