From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: RFC: path relative to current file.
Date: Mon, 15 Oct 2012 17:27:07 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1210151723520.12240@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <507C6C65.8060209@wxs.nl>
>> 2. check if the file "somefile.tex" exists in the directory being
>> popped from the stack.
>> Just for "bug catching"...
>
> it all happens before a file is loaded so the normal reporting is applied
Actually, it is a bit annoying that \environment and \component
do not report an error (or at least a warning message) when the file is
not found. \usemodule at least issues a warning, but does not change the
exit status code, so it is easy to miss the warning message.
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-10-15 21:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 1:34 Andre Caldas
2012-10-15 17:56 ` Hans Hagen
2012-10-15 18:20 ` Hans Hagen
2012-10-15 19:42 ` Andre Caldas
2012-10-15 20:04 ` Hans Hagen
2012-10-15 21:27 ` Aditya Mahajan [this message]
2012-10-15 21:38 ` Marco Patzer
2012-10-15 22:11 ` Hans Hagen
2012-10-15 22:26 ` Andre Caldas
2012-10-16 7:33 ` Hans Hagen
2012-10-16 11:25 ` Andre Caldas
2012-11-03 0:35 ` Andre Caldas
2012-11-03 10:13 ` Sietse Brouwer
2012-11-03 12:47 ` Hans Hagen
2012-11-07 19:34 ` Andre Caldas
2012-11-07 20:35 ` Hans Hagen
2012-11-08 12:14 ` Andre Caldas
2012-11-08 12:43 ` Hans Hagen
2012-11-08 16:30 ` Andre Caldas
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=alpine.LNX.2.02.1210151723520.12240@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).