From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: ConTeXt NTG <ntg-context@ntg.nl>
Subject: \xmlinclude throws no error
Date: Wed, 9 May 2012 14:47:20 +0000 [thread overview]
Message-ID: <ED790354-BD06-4D3E-B4AF-F9C275936923@uva.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 216 bytes --]
Why does \xmlinclude does not throw an error when the file to be read is missing? It causes a mssing file to go unnoticed.
In contrast \xmlprocessfile does throw an error, as expected.
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 1069 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2012-05-09 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ED790354-BD06-4D3E-B4AF-F9C275936923@uva.nl \
--to=h.vandermeer@uva.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).