From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Max Chernoff <mseven@telus.net>
Subject: Re: No error when loading a non-existent module
Date: Fri, 26 Aug 2022 00:45:43 -0600 [thread overview]
Message-ID: <eb09a2e10de65ea38228fdbbd814e215bf055a55.camel@telus.net> (raw)
In-Reply-To: <aeb52e9b-4caf-b777-204a-e63112c263d1@freedom.nl>
On Fri, 2022-08-26 at 07:40 +0200, Hans Hagen wrote:
> On 8/26/2022 3:00 AM, Max Chernoff wrote:
> > Is there a way to make this produce a nice little "error" PDF as soon as
> > the error occurs just like using "\undefined" does?
>
> Only If I add it as option (directive driven, must find some good name
> for it).
You already have errors and warnings as an option, so a good name might
be "fatal"?
> Most modules add commands and that shows immediately. Modules that kick
> in without some command that needs to enable something are sort of
> not-done or rare and experimental only and comparable to when some
> module patches or overloads core functionality withoutr mentioning it.
Here I'm mainly thinking about my lua-widow-control module, which
produces a visual effect, although it can be quite subtle if you're not
paying very close attention.
> > > and if needed can add that line to a local cont-loc.mkxl file so that it
> > > always kicks in.
> >
> > Didn't know about that either.
>
> Ah, that's one of the oldest features: cont-new (for patched before
> updates), cont-loc (for local preferences) and cont-exp (for wolfgang
> and me)
Not seeing anything on the Wiki about either of those. I guess that
means I'm volunteering myself :)
Similarly to "cont-loc.mkxl", is there some local file that is only read
during format generation? Some of my documents use pgf/TikZ and expl3,
and loading these during format generation can save quite a bit of time
when compiling. I know that I can just modify "cont-en.mkxl" or
"context.mkxl", but those can be overwritten by updates.
> > But wouldn't it make sense for this to be an error by default? Nothing
> > good can happen if a user loads a non-existent (or misspelled) module.
> > Loading a non-existent file is a fatal error even in Plain TeX
> > \nonstopmode. I think that making this an error by default would break
> > very few working documents. In exchange, most users would get much more
> > helpful error messages.
> It would never be default because it is quite possible to have cases
> where a module became redundant or is optional. There arte very few
> cases where we are not downward 'command and file' compatible (the most
> noticeable exceptions are when font, language and encoding subsystems
> fundamentally change).
Fair enough.
Thanks,
-- Max
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-08-26 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 0:19 Max Chernoff via ntg-context
2022-08-25 6:57 ` Hans Hagen via ntg-context
2022-08-26 1:00 ` Max Chernoff via ntg-context
2022-08-26 5:40 ` Hans Hagen via ntg-context
2022-08-26 6:45 ` Max Chernoff via ntg-context [this message]
2022-08-26 7:49 ` Hans Hagen via ntg-context
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=eb09a2e10de65ea38228fdbbd814e215bf055a55.camel@telus.net \
--to=ntg-context@ntg.nl \
--cc=mseven@telus.net \
/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).