ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Trace references
Date: Thu, 8 Sep 2016 16:45:34 +0200	[thread overview]
Message-ID: <f7b6eb0f-5bb7-0a27-fdde-d8d23d954f7f@gmail.com> (raw)
In-Reply-To: <57D16BBE.30403@gmail.com>

On 09/08/2016 03:46 PM, Wolfgang Schuster wrote:
>> Henri Menke <mailto:henrimenke@gmail.com>
>> 8. September 2016 um 15:35
>> Dear list,
>>
>> when using cross referencing in my document, LaTeX has the nice warning messages
>>
>> LaTeX Warning: Reference 'foo' on page XX undefined on input line YY.
>> LaTeX Warning: Label `foo' multiply defined.
>> LaTeX Warning: There were undefined references.
>> LaTeX Warning: There were multiply-defined labels.
>>
>> Is there something similar in ConTeXt? The wiki is a little outdated in that regard as \tracereferences does not exist anymore and also is probably not what I'm looking for. I already found \usemodule[references-show] but this only prints annotations on the page.
> You can use trackers:
> 
> \enabletrackers[structures.referencing]
> \enabletrackers[structures.referencing.analyzing]
> \enabletrackers[structures.referencing.identifying]
> \enabletrackers[structures.referencing.importing]
> \enabletrackers[structures.referencing.empty]

Thanks for the pointer, but that is not really what I'm after.  Enabling all these trackers clutters my log all the internal reference information.  I just want to know which ones are undefined and which are duplicate.

Cheers, Henri

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

___________________________________________________________________________________
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:[~2016-09-08 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 13:35 Henri Menke
2016-09-08 13:46 ` Wolfgang Schuster
2016-09-08 14:45   ` Henri Menke [this message]
2016-09-08 16:17     ` Hans Hagen
2016-09-08 16:38       ` Wolfgang Schuster

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=f7b6eb0f-5bb7-0a27-fdde-d8d23d954f7f@gmail.com \
    --to=henrimenke@gmail.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).