ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: metafun: problems, problems & problems again
Date: Mon, 20 Feb 2006 09:36:08 +0100	[thread overview]
Message-ID: <43F97F78.509@wxs.nl> (raw)
In-Reply-To: <6faad9f00602191520s5decf730r7cae44b7125c324@mail.gmail.com>

Mojca Miklavec wrote:
> Hello,
>
> This metafun will soon drive me crazy.
>
> 1. I can't make textext work
>
> Once upon a time I only had problems in MikTeX, now standone is
> causing me problems as well. I have:
> - write18 / -shell-escape enabled
> - \runMPgraphicstrue
>   \runMPTEXgraphicstrue
>   \useMETAFUNformattrue
>   \protectbufferstrue
>   enabled (I don't know where to look further).
> But I still get no figures at all under MikTeX and "undefined" labels
> with the standalone.
>   
that normally means that no tex subruns take place (or wrong ones)

(maybe the system command is not executed, in the log you can see what 
write 18 does)

you can try (on a mp file):

texexec --mptex somefile.mp

and see what is reported


> 2. mptopdf doesn't work under MikTeX (as already mentioned), but
> that's not so critical since I can still use texmfstart or write my
> own .bat file to run it
>   
forget about something mptopdf.exe, the bat method using texmfstart is 
the way to go
> 3. metafun reformats the whole metapost source (including that in
> verbatin) and so you can never predict what will come out; often the
> TeX commands fail to work and while it's possible to easily debug
> plain metapost sources, metafun swallows most of the error warnings
> somehow, so you don't get any output, but no error reports either.
>   
there is normally a <jobname>-mpgraph.log file
> 4. I have problems with \loadfontfilesoncetrue. I searched through
>   
hm, loadfontfilesonce is not there (any more)
> mailing list archives and found out that that problems was already
> present in 2002 and that someone solved it by deleting all ConTeXt
> files from MikTeX. I don't understand why since I have fresh MikTeX
> distribution on the computer, but I'll try that.
>   
maybe some old cont-sys.tex file?
> 5. I hoped to be able to use gnuplot with context terminal, but the
> file I produced crashes pdfetex 1.30.3--2.2 (in stand-alone distro).
> 1.21a under MikTeX doesn't crash, but since there is no output it
> might be that the older version never gets to the point where it would
> crash. A very rare event. The files that make the pdftex crash are
> located here: http://pub.mojca.org/gnuplot/pdftex-crash/
>   
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
-----------------------------------------------------------------

  reply	other threads:[~2006-02-20  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 23:20 Mojca Miklavec
2006-02-20  8:36 ` Hans Hagen [this message]
2006-02-20 19:25   ` Mojca Miklavec
2006-02-20 20:05     ` Taco Hoekwater
2006-02-21 19:01   ` Mojca Miklavec
2006-02-21 21:47     ` Hans Hagen
2006-02-20 11:13 ` Taco Hoekwater

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=43F97F78.509@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).