ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: An error which is not in .log file
Date: Tue, 15 Aug 2023 21:18:54 +0200	[thread overview]
Message-ID: <480729fc-7e64-5f58-1c01-e402e6da0af3@gmx.es> (raw)
In-Reply-To: <20230815173543.53cb359a1b3680f4c0c0e027@posteo.net>

On 8/15/23 17:35, Xavier B. wrote:
> I have the document split in several files.

Hi Xavier,

as someone already mentioned it, the way to check would be:

  mtxrun --scripts check your-document.tex

But this doesn‘t parse \input, so you need to create a loop.

In Unix, it would read something like:

  for i in *.conTeXt; do mtxrun --scripts check $i; done

Windows might require something similar to (inspired by
https://ss64.com/nt/for.html):

  for %%I (*.context) do mtxrun --scripts check %%I

It might report the cause this way.

When ConTeXt quits unexpectedly ("mtx-context | fatal error: return
code: 1" is a error message from the console), it might be a started
command not closed, such as in:

  \starttext
    \startitemize
      \item a
  \stoptext

Just in case it might help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-08-15 19:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 14:50 [NTG-context] " Xavier B.
2023-08-15 15:08 ` [NTG-context] " Hans Hagen
2023-08-15 15:35   ` Xavier B.
2023-08-15 19:18     ` Pablo Rodriguez [this message]
2023-08-15 17:46   ` Xavier B.
2023-08-15 17:54     ` Mikael Sundqvist
2023-08-15 19:13     ` Wolfgang Schuster
2023-08-15 19:36       ` Xavier B.
2023-08-15 19:44         ` Wolfgang Schuster
2023-08-15 22:12           ` Xavier B.
2023-08-16  4:27             ` Wolfgang Schuster
2023-08-16  7:15               ` Xavier B.
2023-08-16 15:02                 ` Wolfgang Schuster
2023-08-16 17:52                   ` Xavier B.
2023-08-19  9:28                   ` Xavier B.
2023-08-16 10:31               ` Aditya Mahajan

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=480729fc-7e64-5f58-1c01-e402e6da0af3@gmx.es \
    --to=oinos@gmx.es \
    --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).