ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: die if a module is missing
Date: Fri, 13 Mar 2009 11:23:38 +0100	[thread overview]
Message-ID: <6faad9f00903130323w38c68eeagb43ee6eb4c2e5fd5@mail.gmail.com> (raw)
In-Reply-To: <m2skljm4ll.fsf@stanford.edu>

On Thu, Mar 12, 2009 at 11:13, Jesse Alama wrote:
> 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.

Hello,

While the problem of silently ignoring the invalid options is indeed
hard to solve and would require rewritting more or less the whole
ConTeXt, issuing an error if module is not found is probably doable
and I would highly support that idea.

I often have that problem as well, but the program usually dies
anyway, with something like
    \starttikzpicture - "command undefined"
a few lines below from where I would expect it to die, so I kind of
know what to do (install a module or switch to a different
distribution).

If user writes \usemodule[this-or-that], he probably wants it to be
loaded. Plain TeX does complain if user says \input this-or-that if
this-or-that.tex is not found.


In connection with that question ... The gnuplot module uses this
command to compile graphics:
    \executesystemcommand{texmfstart --direct gnuplot\space\GNUPLOTfile.plt}

Is there a nice way to check what value gnuplot returns and to make
TeX stop at that point (offering the user to press enter and continue)
on gnuplot failure?

Thanks a lot,
    Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2009-03-13 10:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 10:13 Jesse Alama
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 [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=6faad9f00903130323w38c68eeagb43ee6eb4c2e5fd5@mail.gmail.com \
    --to=mojca.miklavec.lists@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).