ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jannik Voges <researchjavo@icloud.com>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: compilation error in LMTX
Date: Fri, 14 Aug 2020 11:59:31 +0200	[thread overview]
Message-ID: <4a330c86-3027-3447-57b5-9f5d63f90f1b@icloud.com> (raw)
In-Reply-To: <c106d439-2db7-1d69-a477-e0f1ceb83454@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

Hi Wolfgang,


thats a little bit difficult, because the error apparently happens at a
random position in the document (you can add a syntax error in the
document an change the position of the syntax error in the document
until lmtx crashes before it detects the error to get the paragraph
where the crash happens, but that paragraph is fine). And I don't know
why the error happens in one document and not in others (I use similar
commands in affected and not-affected documents; the affected documents
are long but not the longest documents I have) or why it happened two
days ago in one document, which is fine today, and today at another
document (which was fine two days ago). So I don't have a clue how to
reproduce the error.


Jannik


Am 14.08.20 um 11:33 schrieb Wolfgang Schuster:

> Jannik Voges schrieb am 14.08.2020 um 11:29:
>> Hello Hans,
>>
>> I get the error with the newest upload too.
>
> You have to provide a minimal example which produces the error.
>
> Wolfgang
>

[-- Attachment #2: 0x805A4918E8698418.asc --]
[-- Type: application/pgp-keys, Size: 677 bytes --]

[-- Attachment #3: 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
___________________________________________________________________________________

      reply	other threads:[~2020-08-14  9:59 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
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 [this message]

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=4a330c86-3027-3447-57b5-9f5d63f90f1b@icloud.com \
    --to=researchjavo@icloud.com \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@gmail.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).