From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: readfile not understood
Date: Thu, 29 Sep 2011 21:05:45 +0200 [thread overview]
Message-ID: <EA2CEBD8-ABB2-4FD6-ABFA-335168A5CBCB@googlemail.com> (raw)
In-Reply-To: <F97DB8D3-12CD-4F7B-A0F6-E62E27E5F16D@uva.nl>
Am 29.09.2011 um 20:57 schrieb Meer, H. van der:
> I do not understand while \readfile behaves differently from \input with regard to TeX-code processing.
> I have the following code:
>
> \readfile{metapost-setup} %(file with metapost inclusions)
> \starttext
> \startMPpage
> ..
> \stopMPpage
> \stoptext
>
> Replace the \readfile by:
> \input ../../../metapost-setup %(file with metapost inclusions)
> works ok.
> But with \readfile seems to be skipped silently, that is without any sign of it in the log. The convenience of \readfile should be, if I understand correctly, that it searches upwards to the root of directory tree. Which makes the series of ../'s unnecessary and allows for easily pushing the tex-files further down when their number grows.
> Can it be explained?
\readfile expects three arguments, replace it with \ReadFile which expects only one.
Wolfgang
___________________________________________________________________________________
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:[~2011-09-29 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 18:57 Meer, H. van der
2011-09-29 19:05 ` Wolfgang Schuster [this message]
2011-09-29 19:10 ` Meer, H. van der
2011-09-29 19:18 ` Wolfgang Schuster
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=EA2CEBD8-ABB2-4FD6-ABFA-335168A5CBCB@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).