From: Hans Hagen <pragma@wxs.nl>
Subject: Re: compiling project files
Date: Thu, 17 Aug 2006 00:52:06 +0200 [thread overview]
Message-ID: <44E3A196.5010007@wxs.nl> (raw)
In-Reply-To: <44E342AF.4060905@elvenkind.com>
Taco Hoekwater wrote:
> Mojca Miklavec wrote:
>
>> On 8/15/06, Aditya Mahajan wrote:
>>
>>
>>
>>>> 2. When compiling projects that include MPgraphics, I have to run that
>>>> texmfstart line
>>>> above twice to see changes to MPgraphics in my pdf. I thought
>>>>
>>> that one
>>>
>>>
>>>> idea behind
>>>> texexec is that it takes care of all incantations, like "make" in
>>>> programming.
>>>>
>>>>
>>> This should not happen.
>>>
>> I agree with the fact that it should not happen, but it does (perhaps
>> I should say "did", because the last time when I had the problem was
>> once in May; a whole lot of changes have been made since then and I'm
>> not sure if I can find the file which caused me problems again).
>>
>
> IIRC, this problem only crops up when \runMPgraphicstrue is not set
> (so that mpost is run by texexec between TeX runs)
>
normally checksums are made; i must see the failing example
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-08-16 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:52 Derek Schmidt
2006-08-09 16:26 ` Tobias Burnus
2006-08-09 16:27 ` Aditya Mahajan
2006-08-13 3:39 ` Derek Schmidt
2006-08-13 15:46 ` Mojca Miklavec
2006-08-14 20:44 ` Peter Münster
2006-08-15 20:16 ` Boris Tschirschwitz
2006-08-15 20:29 ` Aditya Mahajan
2006-08-16 15:58 ` Mojca Miklavec
2006-08-16 16:07 ` Taco Hoekwater
2006-08-16 22:52 ` Hans Hagen [this message]
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=44E3A196.5010007@wxs.nl \
--to=pragma@wxs.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).