From: Taco Hoekwater <bittext@quicknet.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: smallest possible testfile for mpgraph-error?
Date: Mon, 26 Feb 2001 22:46:19 +0100 [thread overview]
Message-ID: <3A9ACEAB.49163579@quicknet.nl> (raw)
In-Reply-To: <200102261102.MAA00168@sol.cs.uni-dortmund.de>
Patrick Gundlach wrote:
>
> Now I rename simple.mp to mpgraph.mp:
>
> with \protectbufferstrue, mpgraph.1 is ok.
lots of stuff can go wrong with names like mpgraph.mp.
(at least one of them is the shell itself: it caches
i-node numbers, and I've had similar problems with
totally non-TeX related files if and only if the file
was opened for writing without actually unlinking it.
This may not be the problem here, but it is nevertheless
possible).
> mpgraph.mp has been renamed to tmpgraph.kep, then overwritten by
> something (this I dont know, probably the same as above
> (beginfig(1)...) + "end.").
This is texexec: in the subroutine 'checkMPlabels'
> Then mpto opens mpgraph.mp (55 bytes), writes it to tmpgraph.tex). Then \\end is appended > to tmpgraph.tex.
probably mpto
> After that, pdftex is called to create tmpgraph.dvi (208 bytes).
> !! But just before creating the dvi
> file, mpgraph.mp gets overwritten with a single
> "end." line.
This is context itself, that is called to generate the label.
because it doesn't know about protected buffers, it writes
mpgraph.mp. Context does this *always* nowadays, even on the
following sequence of commands:
touch test.tex
texexec test
[press control-d]
The problem is in \initializeMPgraphics, which is part of
\everyjob. The following definition would be a lot safer:
\def\initializeMPgraphics%
{ \immediate\openin\scratchread\MPgraphicfile.mp
\ifeof\scratchread
\immediate\closein\scratchread
\else
\immediate\openout\MPwrite\MPgraphicfile.mp
\immediate\write\MPwrite{end.}%
\immediate\closeout\MPwrite
\fi
\immediate\closein\scratchread
}
I don't see any obvious reason why \protectbufferstrue
shouldn't be the default, btw.
Greetings, Taco
prev parent reply other threads:[~2001-02-26 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 11:02 Patrick Gundlach
2001-02-26 21:46 ` Taco Hoekwater [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=3A9ACEAB.49163579@quicknet.nl \
--to=bittext@quicknet.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).