From: Jannik Voges <jannik.voges@icloud.com>
To: ntg-context@ntg.nl
Subject: Re: compilation error in LMTX
Date: Fri, 14 Aug 2020 11:40:46 +0200 [thread overview]
Message-ID: <1243a208-9302-2bf7-835f-aec1d3f3ef4a@icloud.com> (raw)
In-Reply-To: <864ca6dc-1b9c-0450-2e0c-27a9ba1aa1e6@gmx.es>
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change them
in the future). And by doing so I recognized this error, which seemed to
happen randomly.
Jannik
Am 14.08.20 um 09:26 schrieb Pablo Rodriguez:
> On 8/14/20 8:47 AM, Hans Hagen wrote:
>> On 8/14/2020 2:38 AM, Jannik Voges wrote:
>>> [...]
>>> I have a similar problem with long context-documents (but not all long
>>> context-documents are affected and I don't know what triggers the
>>> error). Sometimes, the errors (error code 139) are happening on second
>>> or third runs (but it might happen on first runs too). When I remove the
>>> chapter where the error happens and all later chapters from the document
>>> it might happen, that the error occurs in an earlier chapter.
>>> In addition to that, documents, which had this error yesterday, can now
>>> be compiled without the problem and other documents without the error
>>> yesterday have the error today. Its really strange.
>>
>> i uploaded a new lmtx but as i'm in the middle of a few things it's a
>> gamble if that solves your problem
>
> Jannik,
>
> it is wise to make a backup of your installed ConTeXt version when
> updating. Especially now that LMTX is in testing mode.
>
> Latest from 2020.08.11 works fine for my huge document, but current
> latest (from today) breaks compilation. So I use latest from 2020.08.11.
>
> Just in case it helps,
>
> Pablo
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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-08-14 9:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 10:49 Pablo Rodriguez
2020-08-14 0:38 ` Jannik Voges
2020-08-14 6:47 ` Hans Hagen
2020-08-14 7:26 ` Pablo Rodriguez
2020-08-14 7:47 ` Hans Hagen
2020-08-15 15:25 ` Pablo Rodriguez
2020-08-15 17:23 ` Hans Hagen
2020-08-15 18:14 ` Pablo Rodriguez
2020-08-15 21:54 ` Pablo Rodriguez
2020-08-15 18:51 ` Pablo Rodriguez
2020-08-14 9:40 ` Jannik Voges [this message]
2020-08-14 9:41 ` Jannik Voges
2020-08-14 11:04 ` Hans Hagen
2020-08-14 11:38 ` Lutz Haseloff
2020-08-14 12:56 ` Jannik Voges
2020-08-14 14:11 ` Hans Hagen
2020-08-14 9:29 ` Jannik Voges
2020-08-14 9:33 ` Wolfgang Schuster
2020-08-14 9:59 ` Jannik Voges
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=1243a208-9302-2bf7-835f-aec1d3f3ef4a@icloud.com \
--to=jannik.voges@icloud.com \
--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).