From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: no graph after compilation
Date: Wed, 11 Aug 2004 18:00:06 +0200 [thread overview]
Message-ID: <411A4286.6010607@seznam.cz> (raw)
In-Reply-To: <m21xidwyad.fsf@levana.de>
>>VZ> Floris, you are not alone. I also have not find the quick solution. So I
>>VZ> call texexec two times when working with MP graphics,
>>VZ> color definitions, ... :-(
>>
>>running it twice is something i can live with, but if it will not
>>solve the problem, then it is... what do i do wrong?
>
>
> Vit and Floris,
>
> if your TeX source is one file only, please do me a favour: try the
> TeX files on live.contextgarden.net and see if the output comes out
> right. If it doesn't, I'd like to know about it. If it does, please
> report on the list. Do you have write18 (texmf.cnf) enabled? How does your
> cont-sys.tex look like? What distribution do you use?
>
> I have (on live..) disabled write18, \runMPgraphicstrue
> and \runMPTEXgraphicstrue.
Thank you, Patrick, I will monitor the case and I will let you know if
it occures again.
I am using two distributions (the case was observed on both):
1) TeX Live 2002/Linux; write18 enabled
2) TeX Live 2003/Win 2K, updated ConTeXt on Win 2000;
write18 disabled for a long time, but it was enabled a month ago
cont-sys.tex (without comments):
\usetypescript [berry] [\defaultencoding]
\runMPgraphicstrue
\runMPTEXgraphicstrue
\useMETAFUNformattrue
\newprettytrue
\protectbufferstrue
Vit
next prev parent reply other threads:[~2004-08-11 16:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 17:30 Some problems with framing typed text Brooks Moses
2004-08-10 18:00 ` Henning Hraban Ramm
2004-08-10 18:47 ` Brooks Moses
2004-08-10 19:04 ` Hans Hagen
2004-08-10 20:35 ` no graph after compilation Floris van Manen
2004-08-11 12:55 ` Peter Rolf
2004-08-11 13:38 ` Re[2]: " Floris van Manen
2004-08-11 14:00 ` Vit Zyka
2004-08-11 14:09 ` Re[2]: " Floris van Manen
2004-08-11 14:21 ` Patrick Gundlach
2004-08-11 14:44 ` Re[2]: " Floris van Manen
2004-08-11 15:07 ` Patrick Gundlach
2004-08-11 15:14 ` Patrick Gundlach
2004-08-11 15:24 ` Re[2]: " Floris van Manen
2004-08-11 15:34 ` Patrick Gundlach
2004-08-11 15:57 ` Re[2]: " Floris van Manen
2004-08-11 16:38 ` Patrick Gundlach
2004-08-11 18:03 ` Re[2]: " Floris van Manen
2004-08-11 18:17 ` Patrick Gundlach
2004-08-11 22:17 ` Re[2]: " Floris van Manen
2004-08-12 7:47 ` Patrick Gundlach
2004-08-12 8:05 ` Eros Albertazzi
2004-08-12 11:30 ` Re[2]: " Floris van Manen
2004-08-12 11:03 ` Vit Zyka
2004-08-12 11:29 ` Re[2]: " Floris van Manen
2004-08-12 19:26 ` Patrick Gundlach
2004-08-12 22:02 ` Hans Hagen
2004-08-12 23:32 ` Re[2]: getting context going Floris van Manen
2004-08-12 23:48 ` Hans Hagen
2004-08-13 8:24 ` Patrick Gundlach
2004-08-13 12:29 ` Re[2]: getting context going --> feature tool request Floris van Manen
2004-08-12 7:25 ` no graph after compilation Hans Hagen
2004-08-12 11:06 ` Re[2]: " Floris van Manen
2004-08-12 7:13 ` Hans Hagen
2004-08-12 7:42 ` Patrick Gundlach
2004-08-11 16:00 ` Vit Zyka [this message]
2004-08-11 16:30 ` Patrick Gundlach
2004-08-11 17:14 ` Re[2]: " Peter Münster
2004-08-10 18:48 ` Some problems with framing typed text Hans Hagen
2004-08-10 19:21 ` Brooks Moses
2004-08-12 10:16 no graph after compilation Duncan Hothersall
2004-08-12 19:06 ` Patrick Gundlach
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=411A4286.6010607@seznam.cz \
--to=vit.zyka@seznam.cz \
--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).