From: Joel via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Gavin <gavinpublic@comcast.net>
Cc: Joel <uaru99@yahoo.com>
Subject: Re: What to do when ConTeXt not revealing the error details?
Date: Mon, 31 Oct 2022 03:24:19 +0000 (UTC) [thread overview]
Message-ID: <394122917.1045807.1667186659875@mail.yahoo.com> (raw)
In-Reply-To: <446D92F1-5698-4505-9FA1-C018C0BC654A@comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 2002 bytes --]
I found what it was, a % in the text preventing a \stopitemize to close a list. Thanks! --Joel
On Sunday, October 30, 2022 at 07:56:44 PM MDT, Gavin <gavinpublic@comcast.net> wrote:
Hi Joel,
I get this error frequently when I forget to stop an environment, for example a \startsection with no \stopsection or a \startplacefigure with no \stopplacefigure. This freqeuntly doesn’t cause an error because the engine is happily packing my entire book into a margin figure.
See if there something you should have stopped near the place where things go bad?
Good luck!
Gavin
> On Oct 30, 2022, at 7:46 PM, Joel via ntg-context <ntg-context@ntg.nl> wrote:
>
> I have a very large document that, when compiled, produces a PDF, but reports the error "mtx-context | fatal error: return code: 1".
>
> The PDF can open, but after about 100 pages in, the content starts appearing all in the wrong place.
>
> Usually when I compile, it says there is an error, and I just scroll up until I find the details. I've scrolled through the output, and *.log file, but cannot see anything that looks like an error.
>
> It could be that just because the document is so long (about 1200 pages), I can't find the error among the huge logs, but I looked through them all carefully.
>
> How can I isolate the error when ConTeXt isn't showing it? Is there some setting for showing only errors, or revealing more details about an error?
>
> --Joel
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4043 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-10-31 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1318153140.1033974.1667180794806.ref@mail.yahoo.com>
2022-10-31 1:46 ` Joel via ntg-context
2022-10-31 1:55 ` Gavin via ntg-context
2022-10-31 3:24 ` Joel via ntg-context [this message]
2022-10-31 3:43 ` Aditya Mahajan via ntg-context
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=394122917.1045807.1667186659875@mail.yahoo.com \
--to=ntg-context@ntg.nl \
--cc=gavinpublic@comcast.net \
--cc=uaru99@yahoo.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).