From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: die if a module is missing
Date: Sat, 14 Mar 2009 20:21:26 +0100 [thread overview]
Message-ID: <49BC03B6.8050602@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0903141507470.32482@ybpnyubfg.ybpnyqbznva>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-14 19:21 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 [this message]
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=49BC03B6.8050602@wxs.nl \
--to=pragma@wxs.nl \
--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).