From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Detecting reference-errors
Date: Wed, 17 Apr 2013 12:55:29 +0200 [thread overview]
Message-ID: <20130417105529.GP5709@homerow> (raw)
In-Reply-To: <516E7A50.9020406@mmnetz.de>
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
On 2013–04–17 "H. Özoguz" wrote:
> With \at[ref] one can get the pagenumber of a reference. If this
> reference is not there (maybe in another file, not included at that
> moment) there is no error given, but two question marks ??.
> That is of course useful, but what if I WANT an error? Because that
> is the only fast way to detect typing errors in references.
ConTeXt requires multiple passes to get the references right, which
means the first run would always fail if missing references trigger
an error and should be delayed to the second run. Seems possible,
though.
I use the following command to detect wrong references. It's not
pretty, but it does it's job reasonably well.
pdftotext <file.pdf> - | grep -E '\?\?|!!'
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-04-17 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 10:32 "H. Özoguz"
2013-04-17 10:55 ` Marco Patzer [this message]
2013-04-17 13:14 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2013-04-17 10:31 "H. Özoguz"
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=20130417105529.GP5709@homerow \
--to=homerow@lavabit.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).