From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Validate (cross)references
Date: Fri, 27 May 2011 23:00:23 +0200 [thread overview]
Message-ID: <4DE010E7.1020706@wxs.nl> (raw)
In-Reply-To: <4FB29C60-7C2C-472F-ABA6-D234FD949727@elvenkind.com>
On 27-5-2011 8:03, Taco Hoekwater wrote:
>
>
>
>
> On 27 mei 2011, at 19:50, Aditya Mahajan<adityam@umich.edu> wrote:
>
>> On Fri, 27 May 2011, Jesse Alama wrote:
>>
>>> Throwing an error would be one way to do this. If throwing an error is not possible, perhaps being able to customize what gets printed when an undefined reference is encountered. E.g., instead of "??", a big, annoying, impossible-to-miss mark in the margin (as one sees when working with overfull lines) or a giant red stopsign saying "UNDEFINED REFERENCE", would do just as well.
>>
>> \def\dummyreference{{\red\bfd UNKNOWN REFERENCE}}
>>
> I think this is good. Undefined references can not simply be converted to errors, because then 'context' stops processing, and of course in any first run there will be undefined references, so you would never get past that if it was simply an error.
>
> But it would also help (for interactive use, at least) if context reported undefined references last, maybe even after the 'x processed pages' line.
there is commented code that writes it to the log; i can make that an
option (directive) if needed
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:[~2011-05-27 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 15:04 Andreas Schneider
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 [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=4DE010E7.1020706@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).