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
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
>> └──
On 9/11/2019 10:14 AM, Vladimir Lomov wrote:
LUAMETATEX:
-- 8< --
tree $TEXMFCACHE/ | sed -e "s@$HOME/.cache/@@"
lmtx/
└── luatex-cache
└── context
└── 5fe67e0bfe781ce0dde776fb1556f32e
├──
Hello,
** Hans Hagen [2019-09-11 10:38:21 +0200]:
> On 9/11/2019 10:14 AM, Vladimir Lomov wrote:
>
>> so I'm sure that this is different "context"s (I'm curious why current
>> version of mkiv files are different but I suppose it is related to other
>> "system" files of context).
>
> the lmtx
On 9/11/2019 10:14 AM, Vladimir Lomov wrote:
so I'm sure that this is different "context"s (I'm curious why current
version of mkiv files are different but I suppose it is related to other
"system" files of context).
the lmtx files can have different solutions because luametatex has some
Hello,
** Hans Hagen [2019-09-11 08:39:03 +0200]:
>
>> but I explicitly set TEXMFCACHE=$HOME/.cache/lmtx (for context suite I
>> set it to $HOME/.cache/context-suite).
>
>>> I'm receiving the super helpful error message:
>>>
>>> ! error (lua): function call: no
>>>
>>> Maybe some sort of
On 9/11/2019 1:19 AM, Henri Menke wrote:
On 9/11/19 3:50 AM, Aditya Mahajan wrote:
On Tue, 10 Sep 2019, Hans Hagen wrote:
On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
Hello,
today I updated lmtx and on simple
$ context --version
I get segfault (in the same time luametatex --version
but I explicitly set TEXMFCACHE=$HOME/.cache/lmtx (for context suite I
set it to $HOME/.cache/context-suite).
I'm receiving the super helpful error message:
! error (lua): function call: no
Maybe some sort of cache versioning is in order to at least give a better error.
It didn't
Hello,
** Henri Menke [2019-09-11 11:19:57 +1200]:
> On 9/11/19 3:50 AM, Aditya Mahajan wrote:
>> On Tue, 10 Sep 2019, Hans Hagen wrote:
>>
>>> On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
Hello,
today I updated lmtx and on simple
$ context --version
I get
Hello,
** Hans Hagen [2019-09-10 17:18:45 +0200]:
> On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
>> Hello,
>> today I updated lmtx and on simple
>>$ context --version
>>
>> I get segfault (in the same time luametatex --version works fine).
>> Running under gdb shows me that the problem might
On 9/11/19 3:50 AM, Aditya Mahajan wrote:
> On Tue, 10 Sep 2019, Hans Hagen wrote:
>
>> On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
>>> Hello,
>>> today I updated lmtx and on simple
>>>
>>>$ context --version
>>>
>>> I get segfault (in the same time luametatex --version works fine).
>>>
On Tue, 10 Sep 2019, Hans Hagen wrote:
On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
Hello,
today I updated lmtx and on simple
$ context --version
I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
On 9/10/2019 4:11 PM, Vladimir Lomov wrote:
Hello,
today I updated lmtx and on simple
$ context --version
I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
calls.
The context from Context Suite
Hello,
today I updated lmtx and on simple
$ context --version
I get segfault (in the same time luametatex --version works fine).
Running under gdb shows me that the problem might be in one of 'realloc'
calls.
The context from Context Suite (mkiv) works fine.
P.S. I tested on two systems,
14 matches
Mail list logo
