From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Halt ConTeXt on Certain Warnings/Errors
Date: Mon, 17 Jun 2013 23:29:28 +0200 [thread overview]
Message-ID: <51BF7FB8.5060508@wxs.nl> (raw)
In-Reply-To: <4F3AF6C4-C523-4C52-B194-1CF4561C92C4@stien.de>
On 6/17/2013 2:05 PM, Malte Stien wrote:
> Hi all,
>
> Is there are way I can have ConTeXt halt on particular warnings or errors? In particular, I like it to spit the dummy when it finds an unknown reference. Otherwise, I end up with the unknown references in the document that I sometimes don't find until much later.
>
> At the moment I grep for "reference" when I run context, as in
>
> context *.tex | grep reference
>
> ...but I thought there might be some more elegant way to do this.
That's not built in. Keep in mind that often multiple passes are used to
resolve references so it would be rather fuzzy too.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-06-17 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 12:05 Malte Stien
2013-06-17 21:29 ` Hans Hagen [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=51BF7FB8.5060508@wxs.nl \
--to=pragma@wxs.nl \
--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).