ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>
Subject: Re: [solved] gnuplot: mpost: Not writing to .log (openout_any = p).
Date: Mon, 12 Dec 2011 09:55:03 +0100	[thread overview]
Message-ID: <4EE5C167.1090508@wxs.nl> (raw)
In-Reply-To: <1323649696.26949.21.camel@mattotaupa>

On 12-12-2011 01:28, Paul Menzel wrote:
> Am Montag, den 12.12.2011, 01:20 +0100 schrieb Paul Menzel:
>
> […]
>
>> I am also getting other errors now and even moving the ConTeXt file to a
>> new directory I keep getting this error from `mpost`.
>>
>>          fonts           : using map file: original-ams-euler
>>          [1.1] [1.1] [1.1] [1.1] [1.1] [1.1] [1.1] [1.1] [1.1] [1.1] [1.1] [1.1]
>>          [1.1] [1.1] [1.1] [1.1]
>>          systems         : end file gnup-gnuplot-1-mp-temp at line 130
>>          (/srv/filme/context/tex/texmf-context/tex/context/base/cont-err.mkii
>>          systems         : no file 'cont-sys.tex', using 'cont-sys.rme' instead
>>          ) )
>>          Output written on gnup-gnuplot-1-mp-temp.dvi (16 pages, 1360 bytes).
>>          Transcript written on gnup-gnuplot-1-mp-temp.log.
>>          TeXExec | runtime: 0.244803
>>
>>          This is MetaPost, version 1.504 (kpathsea version 6.0.0)
>>
>>          mpost: Not writing to .log (openout_any = p).
>>          ! I can't write on file `.log'.
>>          Please type another transcript file name:
>
> Once again I was hit by missing `\{start,stop}text` lines.

even then .. mp cannot write the log because you configuration is 
paranoid (which is what the p means in openout_any) so you need to fix 
your cnf file

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-12-12  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-11 23:51 gnuplot: `! Undefined control sequence.` with format specifier % Paul Menzel
2011-12-12  0:02 ` Mojca Miklavec
2011-12-12  0:20   ` Paul Menzel
2011-12-12  0:27     ` Mojca Miklavec
2011-12-12  0:28     ` [solved] gnuplot: mpost: Not writing to .log (openout_any = p). (was: `! Undefined control sequence.` with format specifier %) Paul Menzel
2011-12-12  8:55       ` Hans Hagen [this message]
2011-12-12  0:13 ` gnuplot: `! Undefined control sequence.` with format specifier % Mojca Miklavec
2011-12-12  0:30   ` Paul Menzel

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=4EE5C167.1090508@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=paulepanter@users.sourceforge.net \
    /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).