From: John Devereux <john@devereux.me.uk>
To: ntg-context@ntg.nl
Subject: Re: die if a module is missing
Date: Fri, 13 Mar 2009 09:14:01 +0000 [thread overview]
Message-ID: <87y6v9dbty.fsf@cordelia.devereux.me.uk> (raw)
In-Reply-To: <49BA1B92.4020903@wxs.nl> (Hans Hagen's message of "Fri\, 13 Mar 2009 09\:38\:42 +0100")
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-13 9:14 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 [this message]
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=87y6v9dbty.fsf@cordelia.devereux.me.uk \
--to=john@devereux.me.uk \
--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).