![](https://secure.gravatar.com/avatar/29c7bbff49b1599eddb2ec73fd9ffa6e.jpg?s=120&d=mm&r=g)
Finding the file works with \ReadFile{} works. But is generates another problem because \input ../../../metapost-setup and \ReadFile{metapost-setup} behave differently! The \input process my \startMPinclusions correctly but the ReadFile does not, because the following metapost has the definitions missing. Hans van der Meer On 29 sep. 2011, at 21:05, Wolfgang Schuster wrote:
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 ___________________________________________________________________________________