* Hans Hagen [May 28, 2004 09:30]:

...

texexec --path=.. masters-project.tex

i suppose that you have a good reason for doing that -) you may try:

Probably not as good a reason as I think, but yes, the reason being that I want all texexec output to go into a separate directory. My directory structure is basically: thesis/ - top level project directory thesis/includes - include files thesis/output - where output goes thesis/thesis - the actual thesis with chapters and so on I don't know of a better way than to run texexec in the thesis/output directory.

\recycleMPslotsfalse

That didn't help, but brought me to the actual problem. \write18 had been disabled somehow (I don't remember reinstalling) and so when I turned \recuclyMPslots to false it made for undefined images instead of the same image over and over and so I figured something else was wrong and sure enough... Thanks for your help, nikolai -- ::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka ::: ::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden ::: ::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 ::: main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

* Henning Hraban Ramm [May 29, 2004 11:11]:

Did you try texexec myfile --result=output/myfile

Yes, I began with that, but the problem is that a lot of files will still go in the same directory as myfile, such as metapost files a .tmp and the .tui file. I guess it's not that bad, but I like keeping things as clean as possible. Perhaps I'm being a bit unreasonable though, cause having the directory structure that I do complicates some stuff (such as includes), nikolai -- ::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka ::: ::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden ::: ::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 ::: main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

* Patrick Gundlach [May 29, 2004 11:50]:

You know about texutil --purgeall ?

No. It seems it's called --purge on my machine, but it seems to do what you're suggesting :-). Perhaps this is a better solution actually. Thanks, nikolai -- ::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka ::: ::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden ::: ::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 ::: main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

Le 28 mai 04, à 21:27, Henning Hraban Ramm a écrit :

Am Freitag, 28.05.04, um 10:16 Uhr (Europe/Zurich) schrieb Nikolai Weibull:

...

Probably not as good a reason as I think, but yes, the reason being that I want all texexec output to go into a separate directory.

Yes, I'd lik that idea very much too! Sometimes, one have many (user) files in the main directory, One can creates subdirectories for well indentified files such as "figures" for all fil related to figure source (xfig, pstricks, matlab,...) But I think all context build files (and file derived from context like metopost files should go **by default** into a separate directory . (but not the main output file such as "myRaport.pdf" !)

Did you try texexec myfile --result=output/myfile

Maurice Diamantini