die if a module is missing

die if a module is missing

[Jesse Alama]

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
___________________________________________________________________________________

Re: die if a module is missing

[Michael Bynum]

This has burned me too.  It would be nice if the errors were more
prominent, perhaps repeated at the end of the output?
Mike



On Thu, Mar 12, 2009 at 6:13 AM, Jesse Alama <alama@stanford.edu> 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.
>
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[John Devereux]

Michael Bynum <mdbynum@gmail.com> writes:


> This has burned me too.  It would be nice if the errors were more
> prominent, perhaps repeated at the end of the output?
> Mike

While we are on the subject, is it possible to make it "die" when
incorrect (non-existent) options are passed to a context command? Is
there any way at all of knowing if the option did anything (even by
examining the log?)

-- 

John Devereux
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Wolfgang Schuster]

Am 12.03.2009 um 15:06 schrieb John Devereux:

> Michael Bynum <mdbynum@gmail.com> writes:
>
>> This has burned me too.  It would be nice if the errors were more
>> prominent, perhaps repeated at the end of the output?
>> Mike
>
> While we are on the subject, is it possible to make it "die" when
> incorrect (non-existent) options are passed to a context command? Is
> there any way at all of knowing if the option did anything (even by
> examining the log?)

No, this is not possible and even such a feature would increase
the compile time a lot, e.g. I used list with valid names in a earlier
version of my letter module and it was 30% slower than the current
version and now imagine what happens if you check each key in a
assignment list.

Wolfgang

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[John Devereux]

Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:

> Am 12.03.2009 um 15:06 schrieb John Devereux:
>
>> Michael Bynum <mdbynum@gmail.com> writes:
>>
>>> This has burned me too.  It would be nice if the errors were more
>>> prominent, perhaps repeated at the end of the output?
>>> Mike
>>
>> While we are on the subject, is it possible to make it "die" when
>> incorrect (non-existent) options are passed to a context command? Is
>> there any way at all of knowing if the option did anything (even by
>> examining the log?)
>
> No, this is not possible and even such a feature would increase
> the compile time a lot, e.g. I used list with valid names in a earlier
> version of my letter module and it was 30% slower than the current
> version and now imagine what happens if you check each key in a
> assignment list.

OK. It seems strange (coming from a programming background). 

If it is only the compile time, then a command line switch might be an
option. (But it sounds like it is inherently hard to do, now).

-- 

John Devereux
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Aditya Mahajan]

On Thu, 12 Mar 2009, John Devereux wrote:

> Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
>
>> Am 12.03.2009 um 15:06 schrieb John Devereux:
>>
>>> Michael Bynum <mdbynum@gmail.com> writes:
>>>
>>>> This has burned me too.  It would be nice if the errors were more
>>>> prominent, perhaps repeated at the end of the output?
>>>> Mike
>>>
>>> While we are on the subject, is it possible to make it "die" when
>>> incorrect (non-existent) options are passed to a context command? Is
>>> there any way at all of knowing if the option did anything (even by
>>> examining the log?)
>>
>> No, this is not possible and even such a feature would increase
>> the compile time a lot, e.g. I used list with valid names in a earlier
>> version of my letter module and it was 30% slower than the current
>> version and now imagine what happens if you check each key in a
>> assignment list.
>
> OK. It seems strange (coming from a programming background).

TeX is no ordinary language. Currently, all keys that you pass are simply 
stored as macros. When a particular option is needed, ConTeXt checks the 
value of the corresponding macro, and decides what to do.

If you want to check the keys, you need that while storing the options as 
macros. This means an extra check for each value for each ConTeXt command. 
Since ConTeXt uses an extensive key-value configuration system, this means 
a lot of extra time. The same argument holds for stripping white spaces 
from key-value pairs. You can use \setupsomething[key=value] but not 
\setupsomething[ key = value ].

For module and environments, this problem can be solved by using

\unprotect
...

\setupsomething[\c!key=\v!value]

...

\protect

> If it is only the compile time, then a command line switch might be an
> option. (But it sounds like it is inherently hard to do, now).

Perhaps with luatex there may be an easier solution. But that would mean 
rewriting how options are handled internally --- a big and error-prone 
task.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Wolfgang Schuster]

Am 12.03.2009 um 16:20 schrieb John Devereux:

> Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
>
>> Am 12.03.2009 um 15:06 schrieb John Devereux:
>>
>>> Michael Bynum <mdbynum@gmail.com> writes:
>>>
>>>> This has burned me too.  It would be nice if the errors were more
>>>> prominent, perhaps repeated at the end of the output?
>>>> Mike
>>>
>>> While we are on the subject, is it possible to make it "die" when
>>> incorrect (non-existent) options are passed to a context command? Is
>>> there any way at all of knowing if the option did anything (even by
>>> examining the log?)
>>
>> No, this is not possible and even such a feature would increase
>> the compile time a lot, e.g. I used list with valid names in a  
>> earlier
>> version of my letter module and it was 30% slower than the current
>> version and now imagine what happens if you check each key in a
>> assignment list.
>
> OK. It seems strange (coming from a programming background).
>
> If it is only the compile time, then a command line switch might be an
> option. (But it sounds like it is inherently hard to do, now).

Yes, something like \traceassignments is possible but you need table
with all valid values (makes only sense in MkIV) and even then a lot
of thing had to be checked. Take as example \localframed (the internal
command for \framed etc.), you could store all of it valid keys in
a table and check against them but what should happen with high level
commands like \externalfigure which use \localframed but use itself
only a subset of the keys, do you want to generate a error message for
the ignored keys (which are valid \localframed keys) or make a  
exception.


Another thing are values for the keys, \setuplayerframed is a  
combination
of \setlayer and \framed and you can set the same values for both with

   \setlayerframed[...][offset=...]

or different values for each part with

   \setlayerframed[...][offset=...][offset=...]

but in the first case not all values are accepted, e.g. 'offset=none'
causes a error message for \setlayer but is a legal setting for \framed.

Wolfgang

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Hans Hagen]

John Devereux wrote:
> Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
> 
>> Am 12.03.2009 um 15:06 schrieb John Devereux:
>>
>>> Michael Bynum <mdbynum@gmail.com> writes:
>>>
>>>> This has burned me too.  It would be nice if the errors were more
>>>> prominent, perhaps repeated at the end of the output?
>>>> Mike
>>> While we are on the subject, is it possible to make it "die" when
>>> incorrect (non-existent) options are passed to a context command? Is
>>> there any way at all of knowing if the option did anything (even by
>>> examining the log?)
>> No, this is not possible and even such a feature would increase
>> the compile time a lot, e.g. I used list with valid names in a earlier
>> version of my letter module and it was 30% slower than the current
>> version and now imagine what happens if you check each key in a
>> assignment list.
> 
> OK. It seems strange (coming from a programming background). 
> 
> If it is only the compile time, then a command line switch might be an
> option. (But it sounds like it is inherently hard to do, now).

i can probably implement some kind of checking (runtime switch, or maybe 
even switch at format generation time) but i will do so only when i've 
completely split of the mkiv code

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: die if a module is missing

[John Devereux]

Hans Hagen <pragma@wxs.nl> writes:

> John Devereux wrote:
>> Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
>>
>>> Am 12.03.2009 um 15:06 schrieb John Devereux:
>>>
>>>> Michael Bynum <mdbynum@gmail.com> writes:
>>>>
>>>>> This has burned me too.  It would be nice if the errors were more
>>>>> prominent, perhaps repeated at the end of the output?
>>>>> Mike
>>>> While we are on the subject, is it possible to make it "die" when
>>>> incorrect (non-existent) options are passed to a context command? Is
>>>> there any way at all of knowing if the option did anything (even by
>>>> examining the log?)
>>> No, this is not possible and even such a feature would increase
>>> the compile time a lot, e.g. I used list with valid names in a earlier
>>> version of my letter module and it was 30% slower than the current
>>> version and now imagine what happens if you check each key in a
>>> assignment list.
>>
>> OK. It seems strange (coming from a programming background). 
>>
>> If it is only the compile time, then a command line switch might be an
>> option. (But it sounds like it is inherently hard to do, now).
>
> i can probably implement some kind of checking (runtime switch, or
> maybe even switch at format generation time) but i will do so only
> when i've completely split of the mkiv code

Hi Hans,

I really don't want to create work if you think it is not
worthwhile. But - as a non-texpert - I do think it is a problem.

It is compounded by:

- Many command options are not documented, so one experiments a lot

- Excess whitespace not only invalidates options, it does so
  silently. The combination is *very* unexpected, and I don't think it
  is that well known. At any rate I used context for 5 years without
  realising something pretty fundamental! (Is it even mentioned in the
  manual?)

  Anyway, the option then has no effect, so one tries a few more...

Thanks,

-- 

John Devereux
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Hans Hagen]

John Devereux wrote:

> I really don't want to create work if you think it is not
> worthwhile. But - as a non-texpert - I do think it is a problem.
> 
> It is compounded by:
> 
> - Many command options are not documented, so one experiments a lot

so .. help us with that -)

> - Excess whitespace not only invalidates options, it does so
>   silently. The combination is *very* unexpected, and I don't think it
>   is that well known. At any rate I used context for 5 years without
>   realising something pretty fundamental! (Is it even mentioned in the
>   manual?)
> 
>   Anyway, the option then has no effect, so one tries a few more...

well, it has to do with what one wants to set up with an option:

a=b,c=d,e= f,g = h

key=value with no space in between; spaces in between will be part of 
the key or value

of course i could be more liberal but it involves a bit more parsing; 
keep in mind that we had this key/value system right from the start 
(long ago) and then speed was more an issue than on todays machines

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: die if a module is missing

[John Devereux]

Hans Hagen <pragma@wxs.nl> writes:

> John Devereux wrote:
>
>> I really don't want to create work if you think it is not
>> worthwhile. But - as a non-texpert - I do think it is a problem.
>>
>> It is compounded by:
>>
>> - Many command options are not documented, so one experiments a lot
>
> so .. help us with that -)

I thought you might say that :) I am hesitant to spread my ignorance,
but I try to help where I think I can.

>> - Excess whitespace not only invalidates options, it does so
>>   silently. The combination is *very* unexpected, and I don't think it
>>   is that well known. At any rate I used context for 5 years without
>>   realising something pretty fundamental! (Is it even mentioned in the
>>   manual?)
>>
>>   Anyway, the option then has no effect, so one tries a few more...
>
> well, it has to do with what one wants to set up with an option:
>
> a=b,c=d,e= f,g = h
>
> key=value with no space in between; spaces in between will be part of
> the key or value
>
> of course i could be more liberal but it involves a bit more parsing;
> keep in mind that we had this key/value system right from the start
> (long ago) and then speed was more an issue than on todays machines

Understood. I *did* in fact use Context productively for the 5 years,
so maybe it is not such a big deal.

-- 

John Devereux
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Wolfgang Schuster]

Am 12.03.2009 um 14:59 schrieb Michael Bynum:

> This has burned me too.  It would be nice if the errors were more
> prominent, perhaps repeated at the end of the output?

This would be indeed nice, a list at the end with all loaded modules
and their current version number.

Wolfgang

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Hans Hagen]

Michael Bynum wrote:
> This has burned me too.  It would be nice if the errors were more
> prominent, perhaps repeated at the end of the output?

ok, i do repeat it now; aborting the run is no options as some modules 
might have been removed due to integration in the core

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: die if a module is missing

[Aditya Mahajan]

On Sat, 14 Mar 2009, Hans Hagen wrote:

> Michael Bynum wrote:
>> This has burned me too.  It would be nice if the errors were more
>> prominent, perhaps repeated at the end of the output?
>
> ok, i do repeat it now; aborting the run is no options as some modules might 
> have been removed due to integration in the core

Then the user should know that and update the source file :-). It can be a 
normal error prompt, the one where you get a question mark and are asked 
if you want to continue or abort (rather than enter the file name prompt 
of \input).

I do feel that for user modules, there should be an error when the module 
is not found. If you do not want the above behaviour as a default, it 
could be a configurable option.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Hans Hagen]

Aditya Mahajan wrote:
> On Sat, 14 Mar 2009, Hans Hagen wrote:
> 
>> Michael Bynum wrote:
>>> This has burned me too.  It would be nice if the errors were more
>>> prominent, perhaps repeated at the end of the output?
>>
>> ok, i do repeat it now; aborting the run is no options as some modules 
>> might have been removed due to integration in the core
> 
> Then the user should know that and update the source file :-). It can be 
> a normal error prompt, the one where you get a question mark and are 
> asked if you want to continue or abort (rather than enter the file name 
> prompt of \input).
> 
> I do feel that for user modules, there should be an error when the 
> module is not found. If you do not want the above behaviour as a 
> default, it could be a configurable option.

needs thinking ... i don't want fully automated flows to abort unseen

configuration is an option but again i first need a mechanism for that 
(and we should all agree on 'what is fatal' and not)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: die if a module is missing

[Hans Hagen]

Aditya Mahajan wrote:
> On Sat, 14 Mar 2009, Hans Hagen wrote:
> 
>> Michael Bynum wrote:
>>> This has burned me too.  It would be nice if the errors were more
>>> prominent, perhaps repeated at the end of the output?
>>
>> ok, i do repeat it now; aborting the run is no options as some modules 
>> might have been removed due to integration in the core
> 
> Then the user should know that and update the source file :-). It can be 
> a normal error prompt, the one where you get a question mark and are 
> asked if you want to continue or abort (rather than enter the file name 
> prompt of \input).
> 
> I do feel that for user modules, there should be an error when the 
> module is not found. If you do not want the above behaviour as a 
> default, it could be a configurable option.

i'm thinking of something \enableoptions[...] (analogue to the mkiv 
\enabletrackers) but then we need to move more configuration options to 
this mechanisms, so it will be something mkiv only

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: die if a module is missing

[Wolfgang Schuster]

On Sun, Mar 15, 2009 at 5:23 PM, Hans Hagen <pragma@wxs.nl> wrote:

>> I do feel that for user modules, there should be an error when the module
>> is not found. If you do not want the above behaviour as a default, it could
>> be a configurable option.
>
> i'm thinking of something \enableoptions[...] (analogue to the mkiv
> \enabletrackers) but then we need to move more configuration options to this
> mechanisms, so it will be something mkiv only

You could move all tracing parameters in a comma list but I prefer than
a different name like \enabletracing[table,layer,...]. For the modules you could
use the two command \enablemodulenotfounderror with a 'wait' message on
the termal and \disablemodulenotfounderror (default) to ignore missing modules.

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: die if a module is missing

[Hans Hagen]

Wolfgang Schuster wrote:
> On Sun, Mar 15, 2009 at 5:23 PM, Hans Hagen <pragma@wxs.nl> wrote:
> 
>>> I do feel that for user modules, there should be an error when the module
>>> is not found. If you do not want the above behaviour as a default, it could
>>> be a configurable option.
>> i'm thinking of something \enableoptions[...] (analogue to the mkiv
>> \enabletrackers) but then we need to move more configuration options to this
>> mechanisms, so it will be something mkiv only
> 
> You could move all tracing parameters in a comma list but I prefer than
> a different name like \enabletracing[table,layer,...]. For the modules you could

tracing is something different (will be part of the tracker)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: die if a module is missing

[Mojca Miklavec]

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
___________________________________________________________________________________