From: Henning Hraban Ramm <texml@fiee.net>
To: Joel via ntg-context <ntg-context@ntg.nl>
Subject: [NTG-context] Re: How to isolate serious errors from warnings?
Date: Thu, 18 Apr 2024 08:26:30 +0200 [thread overview]
Message-ID: <e858d02e-2589-43d8-b417-4c5286ce5f8c@fiee.net> (raw)
In-Reply-To: <1245125740.301939.1713398996808@mail.yahoo.com>
Am 18.04.24 um 02:09 schrieb Joel via ntg-context:
> I'm about to have a lengthy (2,000+ page) document published. Normally
> if it compiles and looks okay, I regard that as meaning no errors
> appeared, but I've noticed that sometimes ConTeXt will still compile,
> even if something isn't displayed on screen as it should:
>
> (1) I tried placing a table inside a startitemize environment, as
> instead of it not compiling, it left a message in the document warning
> that wasn't supported.
>
> (2) In another case, I had an image that ConTeXt couldn't find, as I
> mispelled the filenmame, and it fully compiled and made a PDF, without
> me noticing.
>
> (3) Or maybe in some case, a font couldn't be found for a specific
> character, so a single character in the file isn't displaying.
>
> Those are just some examples; I intended for something to be printed on
> the PDF, but it isn't showing there.
>
> Since a document of this size will have a lot of messages, is there a
> way to adjust the settings, from "show everything" to "show some" to
> "show only serious errors"? Or maybe to use > to send the errors to
> another file for careful study? (using Linux if that matters)
You can enable trackers like
\enabletrackers[figures.*]
But that just gives more log messages for debugging.
You get the list of all trackers with:
context --global m-trackers.mkiv
For your use case, directives are more helpful, like
\enabledirectives[logs.errors=*] (i.e. break at every error)
AFAIK that just handles missing characters, references and modules ATM,
but this information might be outdated.
You get all directives with
context --global m-directives.mkiv
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-04-18 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1245125740.301939.1713398996808.ref@mail.yahoo.com>
2024-04-18 0:09 ` [NTG-context] " Joel via ntg-context
2024-04-18 6:26 ` Henning Hraban Ramm [this message]
2024-04-19 13:56 ` [NTG-context] " Hans Hagen
2024-04-20 9:20 ` Bruce Horrocks
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=e858d02e-2589-43d8-b417-4c5286ce5f8c@fiee.net \
--to=texml@fiee.net \
--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).