ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andreas Schneider <aksdb@gmx.de>
To: ntg-context@ntg.nl
Subject: Validate (cross)references
Date: Fri, 27 May 2011 17:04:42 +0200	[thread overview]
Message-ID: <15410263440.20110527170442@gmx.de> (raw)

Hello,

if  I  use  \in,  \about,  \at  or  anything  else  that  generates  a
cross-reference,  and  that  reference  happens to be invalid (typo or
whatever),  it  just  prints  out  "nothing".  Is  there a way to have
context throw an error if a reference is invalid? (That probably would
only  make  sense  in the second pass of context, since the first pass
has to collect the references first.)

If context can't do it by itself, I'll probably just grep for "unknown
reference"  and  use  that,  but  if context could do it by itself, it
would be nice for automated builds (I actually have my current ConTeXt
project in a Continous Integration system, so anything that leads to a
wrong result should throw an error there.)

-- 
Best Regards,
Andreas

___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2011-05-27 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 15:04 Andreas Schneider [this message]
2011-05-27 15:09 ` Wolfgang Schuster
2011-05-27 15:19   ` Andreas Schneider
2011-05-27 16:58     ` Jesse Alama
2011-05-27 17:50       ` Aditya Mahajan
2011-05-27 18:03         ` Taco Hoekwater
2011-05-27 21:00           ` 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=15410263440.20110527170442@gmx.de \
    --to=aksdb@gmx.de \
    --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).