From: Jesse Alama <alama@stanford.edu>
To: ntg-context@ntg.nl
Subject: die if a module is missing
Date: Thu, 12 Mar 2009 03:13:10 -0700 [thread overview]
Message-ID: <m2skljm4ll.fsf@stanford.edu> (raw)
I was recently debugging some presentation that I was working on in
ConTeXt and found, to my surprise, that the problem was that I was using
\usemodule[blah-blah]
but there was no such module called blah-blah. The output does indeed
say that there was no such module, but I didn't see that. Is there a
way to set up modules so that, if a module isn't found, an error is
generated and the TeX run is stopped? I would have discovered the
source of my problem more quickly had I been able to set things up in
that way.
Thanks,
Jesse
--
Jesse Alama (alama@stanford.edu)
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2009-03-12 10:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 10:13 Jesse Alama [this message]
2009-03-12 13:59 ` Michael Bynum
2009-03-12 14:06 ` John Devereux
2009-03-12 14:19 ` Wolfgang Schuster
2009-03-12 15:20 ` John Devereux
2009-03-12 15:38 ` Aditya Mahajan
2009-03-12 15:38 ` Wolfgang Schuster
2009-03-13 8:38 ` Hans Hagen
2009-03-13 9:14 ` John Devereux
2009-03-13 9:31 ` Hans Hagen
2009-03-13 10:35 ` John Devereux
2009-03-12 14:21 ` Wolfgang Schuster
2009-03-14 19:05 ` Hans Hagen
2009-03-14 19:13 ` Aditya Mahajan
2009-03-14 19:21 ` Hans Hagen
2009-03-15 16:23 ` Hans Hagen
2009-03-16 12:14 ` Wolfgang Schuster
2009-03-16 13:27 ` Hans Hagen
2009-03-13 10:23 ` Mojca Miklavec
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=m2skljm4ll.fsf@stanford.edu \
--to=alama@stanford.edu \
--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).