From: Kai Straube <kai.straube@gmx.de>
Cc: pragma@wxs.nl
Subject: Re: ntg-context Digest, Vol 6, Issue 37
Date: Fri, 17 Dec 2004 22:13:18 +0100 [thread overview]
Message-ID: <200412172213.18330.kai.straube@gmx.de> (raw)
In-Reply-To: <20041217110002.688E7127AC@ronja.ntg.nl>
Hans Hagen wrote:
> can you try
>
> texexec --pdf --automp yourfile
>
> it may be that your context is configured for runtime mp processing while
> your tex does not have write18 enabled
Thank you for your answer,
but this results in no other output ;-(
Kai
next parent reply other threads:[~2004-12-17 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041217110002.688E7127AC@ronja.ntg.nl>
2004-12-17 21:13 ` Kai Straube [this message]
2004-12-18 22:42 ` h h extern
2004-12-19 20:23 ` No bonds visibel with ppchtex Kai Straube
2004-12-31 21:22 ` Hans Hagen
2005-01-04 21:40 ` Kai Straube
[not found] ` <41DC1DD9.2020407@wxs.nl>
2005-01-06 9:04 ` Kai Straube
2005-01-06 12:01 ` Hans Hagen
2005-01-06 21:15 ` Kai Straube
2005-01-07 13:28 ` \dostopfloattext problem Martin Kolarík
2005-01-07 14:23 ` m-letter (addressee) Rob Ermers
2005-01-09 20:06 ` \dostopfloattext problem h h extern
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=200412172213.18330.kai.straube@gmx.de \
--to=kai.straube@gmx.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).