ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: errors
Date: Wed, 27 Sep 2017 10:51:36 +0200	[thread overview]
Message-ID: <3FF8516B-0FB9-43B5-AA83-4280B8F42DCA@elvenkind.com> (raw)
In-Reply-To: <3f7dcaa9-ed5c-fe47-8481-8abacde4c342@wxs.nl>

Hi Hans,

Thanks, this is very useful already. A small request though, could you
wrap (or precede) those messages with a message like:

  system          > start problem reporting
  …
  [system          > stop problem reporting]

or (even better) move all of those messages to a dedicated ‘problems’
message group like this?

  problems         > start missing files

I want to be able to use grep on the log / terminal quickly to find whether
there are any such problems.


Best wishes,
Taco


> On 25 Sep 2017, at 19:19, Hans Hagen <pragma@wxs.nl> wrote:
> 
> Hi,
> 
> At the context meeting there was a bit of discussion about error messages. I looked into that a bit an ddecided to provide a summay option. The following text:
> 
> \enabledirectives[logs.errors] % context --errors
> 
> \setupinteraction[state=start]
> 
> \environment is-not-there
> 
> \usemodule[x][foobar]
> 
> \starttext
> 
> \chapter[foo]{foo}
> 
> \in{foo}[foo]
> \in{bar}[bar]
> 
> \chapter[bar]{bar}
> 
> \in{foo}[foo]
> \in{bar}[bar]
> 
> \xmlload{main}{crapcrap.xml}{}
> 
> oeps \in{foo}[foo-a] oeps \char 999 \par
> oeps \in{foo}[foo-a] oeps \char 995 \par
> oeps \in{foo}[foo-b] oeps \char 991 \par
> 
> \externalfigure[dummy]
> 
> \dorecurse {10} {
>    \samplefile{sapolsky}
>    {\sl  \char 999 \char 995 \char 991}
>    {\bf  \char 999 \char 995 \char 991}
>    {\bfa \char 999 \char 995 \char 991}
>    {\bfb \char 999 \char 995 \char 991}
>    {\bfc \char 999 \char 995 \char 991}
>    \par
> }
> 
> \stoptext
> 
> will produce (at the end of a run):
> 
> system          > start missing files
> system          >       tex  is-not-there
> system          > stop missing files
> 
> modules         > start missing modules
> modules         >       x-foobar
> modules         > stop missing modules
> 
> lxml            > start problematic xml files
> lxml            >    1  crapcrap.xml
> lxml            > stop problematic xml files
> 
> references      > start missing references
> references      >    4  [][foo-a]
> references      >    2  [][foo-b]
> references      > stop missing references
> 
> fonts           > start missing characters: c:/data/develop/tex-context/tex/texmf/fonts/opentype/public/lm/lmroman10-bold.otf
> fonts           >   90  U+003DF  ϟ  GREEK SMALL LETTER KOPPA
> fonts           >   90  U+003E3  ϣ  COPTIC SMALL LETTER SHEI
> fonts           >   90  U+003E7  ϧ  COPTIC SMALL LETTER KHEI
> fonts           > stop missing characters
> 
> fonts           > start missing characters: c:/data/develop/tex-context/tex/texmf/fonts/opentype/public/lm/lmroman12-bold.otf
> fonts           >   10  U+003DF  ϟ  GREEK SMALL LETTER KOPPA
> fonts           >   10  U+003E3  ϣ  COPTIC SMALL LETTER SHEI
> fonts           >   10  U+003E7  ϧ  COPTIC SMALL LETTER KHEI
> fonts           > stop missing characters
> 
> fonts           > start missing characters: c:/data/develop/tex-context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
> fonts           >    1  U+003DF  ϟ  GREEK SMALL LETTER KOPPA
> fonts           >    1  U+003E3  ϣ  COPTIC SMALL LETTER SHEI
> fonts           >    1  U+003E7  ϧ  COPTIC SMALL LETTER KHEI
> fonts           > stop missing characters
> 
> fonts           > start missing characters: c:/data/develop/tex-context/tex/texmf/fonts/opentype/public/lm/lmromanslant12-regular.otf
> fonts           >   10  U+003DF  ϟ  GREEK SMALL LETTER KOPPA
> fonts           >   10  U+003E3  ϣ  COPTIC SMALL LETTER SHEI
> fonts           >   10  U+003E7  ϧ  COPTIC SMALL LETTER KHEI
> fonts           > stop missing characters
> 
> graphics        > start missing figures
> graphics        >       dummy
> graphics        > stop missing figures
> 
> In order to get the missing characters message we currently need to say
> 
> \enabletrackers[fonts.missing]
> 
> (which btw has some options, see manual)  but in a next update of luatex you will get the log without this too.
> 
> Specially for Taco there is:
> 
> \enabledirectives[logs.errors=missing characters]
> 
> which will quit with an exit state 1 (given that he runs an upcoming version of luatex).
> 
> It was not that trivial to achieve this but at least it's there (soon).
> 
> Hans
> 
> 
> 
> -----------------------------------------------------------------
>                                          Hans Hagen | PRAGMA ADE
>              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>       tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

Taco Hoekwater
Elvenkind BV




___________________________________________________________________________________
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:[~2017-09-27  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 17:19 errors Hans Hagen
2017-09-27  8:51 ` Taco Hoekwater [this message]
2017-09-27 10:23   ` errors Hans Hagen

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=3FF8516B-0FB9-43B5-AA83-4280B8F42DCA@elvenkind.com \
    --to=taco@elvenkind.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).