On 27-5-2011 8:03, Taco Hoekwater wrote:
On 27 mei 2011, at 19:50, Aditya Mahajan<[email protected]> 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 : [email protected] / 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
___________________________________________________________________________________
