ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: "Denis B. Roegel" <Denis.Roegel@loria.fr>,
	ntg-context@ntg.nl, roegel@lorraine.loria.fr
Subject: Re: compilation is stuck!
Date: 03 Nov 2000 10:49:41 -0500	[thread overview]
Message-ID: <m3pukd12ei.fsf@coe.uga.edu> (raw)
In-Reply-To: Hans Hagen's message of "Thu, 02 Nov 2000 13:28:11 +0100"

Hans Hagen <pragma@wxs.nl> writes:

> At 01:15 PM 11/2/00 +0100, Denis B. Roegel wrote:
> >
> >> In what sense? It runsok here. 
> >
> >With 
> >
> >\setupcolors[state=start]
> >\starttext
> >\startMPenvironment
> >  \setupbodyfont[pos]
> >\stopMPenvironment
> >\startMPcode
> >  draw btex Meta is a female lion! etex
> >  xysized (\the\textwidth,\the\textheight);
> >\stopMPcode
> >\stoptext
> 
> I cannot get this hung, nor with pdftex, pdfetex, dvips output, dvipsone
> output, pdf output. Can someone else try this on his linux box? [with
> latest version that has metafun support]

When texexec looks hung it is often asking for input:

              run time : 1 seconds
       dvi to metapost : mpgraph
              metapost : mpgraph
                format : metafun
This is MetaPost, Version 0.641 (Web2C 7.3.1)
Sorry, I can't find the mem file `metafun.mem'; will try `mpost.mem'.
(mpgraph.mp)
*

... and it's waiting for the user to type a response.  I have never
gotten used to working with tex interactively, so I use makefiles that
redirect texexec's standard input from /dev/null.  

Doing that you get quick failure instead of hanging, so you can check
the log files.

Try something like this:

        texexec --pdf test < /dev/null

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/


  parent reply	other threads:[~2000-11-03 15:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 12:15 Denis B. Roegel
2000-11-02 12:28 ` Hans Hagen
2000-11-03 15:31   ` Denis B. Roegel
2000-11-03 15:49   ` Ed L Cashin [this message]
2000-11-03 15:58     ` Denis B. Roegel
2000-11-03 16:10       ` Ed L Cashin
2000-11-03 16:16         ` Denis B. Roegel
2000-11-03 16:55       ` Hans Hagen
2000-11-03 19:27         ` Denis B. Roegel
2000-11-03 16:57       ` Hans Hagen
2000-11-03 19:45         ` Denis B. Roegel
2000-11-04 15:15           ` Hraban
2000-11-05 20:52             ` Hans Hagen
2000-11-06 15:47               ` Taco Hoekwater
2000-11-07 18:54               ` Fonts (Was: compilation is stuck!) Hraban
2000-11-05 20:18           ` compilation is stuck! Hans Hagen
2000-11-08 12:37             ` compilation is stuck! (problems with postscript fonts on unix) Uwe Koloska
  -- strict thread matches above, loose matches on Subject: below --
2000-11-01 21:22 compilation is stuck! Denis B. Roegel
2000-11-02  8:13 ` Hans Hagen

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=m3pukd12ei.fsf@coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    --cc=Denis.Roegel@loria.fr \
    --cc=ntg-context@ntg.nl \
    --cc=roegel@lorraine.loria.fr \
    /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).