ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nikolai Weibull <context-list@pcppopper.org>
Subject: Re: Overwritten metapost files
Date: Fri, 28 May 2004 10:16:26 +0200	[thread overview]
Message-ID: <20040528081625.GB4964@puritan.pcp.ath.cx> (raw)
In-Reply-To: <6.0.1.1.2.20040527224643.01cb7d48@localhost>

* Hans Hagen <pragma@wxs.nl> [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);}

  reply	other threads:[~2004-05-28  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 15:47 Nikolai Weibull
2004-05-27 20:48 ` Hans Hagen
2004-05-28  8:16   ` Nikolai Weibull [this message]
2004-05-28 19:27     ` Henning Hraban Ramm
2004-05-29  9:36       ` Nikolai Weibull
2004-05-29  9:47         ` Patrick Gundlach
2004-05-29 10:01           ` Nikolai Weibull
2004-05-29 10:11             ` Patrick Gundlach
2004-05-29 12:55       ` Maurice Diamantini
2004-06-01 18:45         ` Hans Hagen

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=20040528081625.GB4964@puritan.pcp.ath.cx \
    --to=context-list@pcppopper.org \
    --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).