metapost: unable to make mpx file error

metapost: unable to make mpx file error

[Alan BRASLAU]

\startOT
	Wow! "experimental metapost version two"
	(does this mean that we get to play with precision?)
\stopOT

\startQUESTION
	The following minimal example yields an error:

\starttext
\startMPcode
	input circle ;
\stopMPcode
\stoptext

	where circle.mp contains a btex...etex sequence: 

draw fullcircle scaled 1cm ;
label (btex 1 cm etex , (0,0)) ;


	The "input circle ;" will work if I comment-out or remove label ;
	The minimal example will work, of course, if the mp code is
	in my tex file.

	The error message is:


mplib           : loading 'metafun.mp' (experimental metapost version two)
! mp terminal: (circle.mp
>> circle.mp
>> circle.mpx
! Unable to make mpx file.
l.2 label (btex
                1 cm etex , (0,0));

.

system          > error on line 4 in file mp.tex: mp terminal: (circle.mp
>> circle.mp
>> circle.mpx
! Unable to make mpx file.
l.2 label (btex
                1 cm etex , (0,0));

 ...

1     \starttext
2     \startMPcode
3       input circle ;
4 >>  \stopMPcode
5     \stoptext

<inserted text> ...re.mp ; fi ; ;;;;]===], false)}
                                                  
\processMPgraphic ...e ;\!!es , \MPaskedfigure )}}
                                                  \egroup \placeMPgraphic 
\d...
l.4 \stopMPcode
               

\stopQUESTION

Alan
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: metapost: unable to make mpx file error

[Hans Hagen]

On 28-9-2010 4:08, Alan BRASLAU wrote:
> \startOT
> 	Wow! "experimental metapost version two"
> 	(does this mean that we get to play with precision?)
> \stopOT
>
> \startQUESTION
> 	The following minimal example yields an error:
>
> \starttext
> \startMPcode
> 	input circle ;
> \stopMPcode
> \stoptext
>
> 	where circle.mp contains a btex...etex sequence:
>
> draw fullcircle scaled 1cm ;
> label (btex 1 cm etex , (0,0)) ;
>
>
> 	The "input circle ;" will work if I comment-out or remove label ;
> 	The minimal example will work, of course, if the mp code is
> 	in my tex file.
>
> 	The error message is:
>
>
> mplib           : loading 'metafun.mp' (experimental metapost version two)
> ! mp terminal: (circle.mp
>>> circle.mp
>>> circle.mpx
> ! Unable to make mpx file.
> l.2 label (btex
>                  1 cm etex , (0,0));
>
> ..
>
> system>  error on line 4 in file mp.tex: mp terminal: (circle.mp
>>> circle.mp
>>> circle.mpx
> ! Unable to make mpx file.

hm, looks like I have to intercept the inputs in order to turn the btex 
... into textexts (which happens with the main file)

what I actually need for this is a reader hook (just like we have a 
finder hook); I could use the finder hook to make a temporary file, but 
I wonder if that makes sense so let's first check if we can get a reader 
hook

(remind me in a few weeks anyway and use textext instead of btex/etex 
for the moment)

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
___________________________________________________________________________________

Re: Custom lua script (updating and debugging)

[Stefan Müller]

Hi,

thanks for the fast reply Mojca! Unfortunately it is still not working. Here 
is what I did. I'm afraid it has possibly more to do with pretty printers in 
particular (than lua scripts in general), but actually I have no idea.

I took the file
  MyConTeXtDir/tex/texmf-context/tex/context/base/pret-lua.lua
and copied it to
  MyConTeXtDir/tex/texmf-local/tex/context/user/pret-pas.lua
Next I replaced every occurance of "lua" in this new file by "pas" (so this 
changed the name of one function and renamed the visualizer itself). Then I 
ran "context --generate".

My testfile is added below. The "end" is typeset as if pret-pas.lua wouldn't 
exist. If I change "option=PAS" to "option=LUA" it works as intended ("end" is 
green). What is going on here? Any help is appreciated.

\installprettytype[PAS][PAS]
\setupcolors[state=start]
\setuptyping[option=color]
\definetyping[PAS][option=PAS, escape=yes, tab=4, numbering=line]

\starttext \startPAS
end
\stopPAS \stoptext

Thanks in advance,
Stefan.

PS: Additional question: Is it possible to integrate "option=color" into the 
"\definetyping[PAS]"? option={PAS,color}?
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Custom lua script (updating and debugging)

[Stefan Müller]

Sorry for replying to the wrong thread...

I just wanted to say that it works now. I justed started again from 
scratch and did the same as below. No idea what caused the trouble.

Thanks again,
Stefan.

On 28.09.2010 23:53, Stefan Müller wrote:
> Hi,
>
> thanks for the fast reply Mojca! Unfortunately it is still not working. Here
> is what I did. I'm afraid it has possibly more to do with pretty printers in
> particular (than lua scripts in general), but actually I have no idea.
>
> I took the file
>    MyConTeXtDir/tex/texmf-context/tex/context/base/pret-lua.lua
> and copied it to
>    MyConTeXtDir/tex/texmf-local/tex/context/user/pret-pas.lua
> Next I replaced every occurance of "lua" in this new file by "pas" (so this
> changed the name of one function and renamed the visualizer itself). Then I
> ran "context --generate".
>
> My testfile is added below. The "end" is typeset as if pret-pas.lua wouldn't
> exist. If I change "option=PAS" to "option=LUA" it works as intended ("end" is
> green). What is going on here? Any help is appreciated.
>
> \installprettytype[PAS][PAS]
> \setupcolors[state=start]
> \setuptyping[option=color]
> \definetyping[PAS][option=PAS, escape=yes, tab=4, numbering=line]
>
> \starttext \startPAS
> end
> \stopPAS \stoptext
>
> Thanks in advance,
> Stefan.
>
> PS: Additional question: Is it possible to integrate "option=color" into the
> "\definetyping[PAS]"? option={PAS,color}?
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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
___________________________________________________________________________________

Custom lua script (updating and debugging)

[Stefan Müller]

Hi list,

I'm currently messing around with a custom lua script (a pretty printer) 
and I have some beginner trouble.

First: I put the file in "MyContexDir\tex\texmf\tex\context\base\". What 
do I have to do to let ConTeXt work with the script and to let ConTeXt 
know that something has changed in the script? Is "context --generate" 
enough (after initializing with "setuptex.bat")?

Second: How can I debug errors in my *.lua file? Just put
   print("debug message")
in the function that is (supposed to be) called?

Any help appreciated and thanks in advance!

Stefan
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Custom lua script (updating and debugging)

[Mojca Miklavec]

On Tue, Sep 28, 2010 at 12:41, Stefan Müller wrote:
> Hi list,
>
> I'm currently messing around with a custom lua script (a pretty printer) and
> I have some beginner trouble.
>
> First: I put the file in "MyContexDir\tex\texmf\tex\context\base\".

Put them into
    MyContexDir\tex\texmf-local\tex\context\user\
because:
- You need to use texmf-local instead of texmf, else your file might
be deleted when you update the distribution.
- It doesn't really matter where the file is as long as it is under
[TEXMF]\tex\context, but using "user" is somehow more sensible than
"base".

> What do
> I have to do to let ConTeXt work with the script and to let ConTeXt know
> that something has changed in the script? Is "context --generate" enough
> (after initializing with "setuptex.bat")?

You need to use context --generate only when you add the script for
the first time. After you modify it, you don't need to do anything
unless you are changing ConTeXt source. If you change ConTeXt source,
you need to also run "context --make" (but that would be dangerous
anyway).

> Second: How can I debug errors in my *.lua file? Just put
>  print("debug message")
> in the function that is (supposed to be) called?

Yes, or tex.print (depending on how you want to debug).

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Custom lua script (updating and debugging)

[Procházka Lukáš Ing. - Pontex s. r. o.]

Hello,

I have also the experience that when the Lua file is placed where the LUA_PATH system variable points (or: see the documentation how exactly LUA_PATH works), than I can use the 'require' command and the Lua file will be found.

E.g.:

LUA_PATH = (...);C:\MyDir\?.lua

C:\MyDir\MyFile.lua:

print("This is MyFile.lua")

And a ctx file:

\startluacode
   require("MyFile")
\stopluacode

- Will print "This is MyFile.lua" to the output stream when converting .tex to (e.g.) .pdf.

Lukas


On Tue, 28 Sep 2010 21:30:32 +0200, Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:

> On Tue, Sep 28, 2010 at 12:41, Stefan Müller wrote:
>> Hi list,
>>
>> I'm currently messing around with a custom lua script (a pretty printer) and
>> I have some beginner trouble.
>>
>> First: I put the file in "MyContexDir\tex\texmf\tex\context\base\".
>
> Put them into
>     MyContexDir\tex\texmf-local\tex\context\user\
> because:
> - You need to use texmf-local instead of texmf, else your file might
> be deleted when you update the distribution.
> - It doesn't really matter where the file is as long as it is under
> [TEXMF]\tex\context, but using "user" is somehow more sensible than
> "base".
>
>> What do
>> I have to do to let ConTeXt work with the script and to let ConTeXt know
>> that something has changed in the script? Is "context --generate" enough
>> (after initializing with "setuptex.bat")?
>
> You need to use context --generate only when you add the script for
> the first time. After you modify it, you don't need to do anything
> unless you are changing ConTeXt source. If you change ConTeXt source,
> you need to also run "context --make" (but that would be dangerous
> anyway).
>
>> Second: How can I debug errors in my *.lua file? Just put
>>  print("debug message")
>> in the function that is (supposed to be) called?
>
> Yes, or tex.print (depending on how you want to debug).
>
> Mojca
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>


-- 
Ing. Lukáš Procházka [mailto:LPr@pontex.cz]
Pontex s. r. o.      [mailto:pontex@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4

Tel: +420 244 062 238
Fax: +420 244 461 038

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Custom lua script (updating and debugging)

[Hans Hagen]

On 29-9-2010 8:50, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
> Hello,
>
> I have also the experience that when the Lua file is placed where the
> LUA_PATH system variable points (or: see the documentation how exactly
> LUA_PATH works), than I can use the 'require' command and the Lua file
> will be found.
>
> E.g.:
>
> LUA_PATH = (...);C:\MyDir\?.lua
>
> C:\MyDir\MyFile.lua:
>
> print("This is MyFile.lua")
>
> And a ctx file:
>
> \startluacode
> require("MyFile")
> \stopluacode
>
> - Will print "This is MyFile.lua" to the output stream when converting
> .tex to (e.g.) .pdf.

texmf-[local|project]/scripts/context/lua

should work out ok with require, given that you also have regenerated 
the file database

> Lukas
>
>
> On Tue, 28 Sep 2010 21:30:32 +0200, Mojca Miklavec
> <mojca.miklavec.lists@gmail.com> wrote:
>
>> On Tue, Sep 28, 2010 at 12:41, Stefan Müller wrote:
>>> Hi list,
>>>
>>> I'm currently messing around with a custom lua script (a pretty
>>> printer) and
>>> I have some beginner trouble.
>>>
>>> First: I put the file in "MyContexDir\tex\texmf\tex\context\base\".
>>
>> Put them into
>> MyContexDir\tex\texmf-local\tex\context\user\
>> because:
>> - You need to use texmf-local instead of texmf, else your file might
>> be deleted when you update the distribution.
>> - It doesn't really matter where the file is as long as it is under
>> [TEXMF]\tex\context, but using "user" is somehow more sensible than
>> "base".
>>
>>> What do
>>> I have to do to let ConTeXt work with the script and to let ConTeXt know
>>> that something has changed in the script? Is "context --generate" enough
>>> (after initializing with "setuptex.bat")?
>>
>> You need to use context --generate only when you add the script for
>> the first time. After you modify it, you don't need to do anything
>> unless you are changing ConTeXt source. If you change ConTeXt source,
>> you need to also run "context --make" (but that would be dangerous
>> anyway).
>>
>>> Second: How can I debug errors in my *.lua file? Just put
>>> print("debug message")
>>> in the function that is (supposed to be) called?
>>
>> Yes, or tex.print (depending on how you want to debug).
>>
>> Mojca
>> ___________________________________________________________________________________
>>
>> 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
>> ___________________________________________________________________________________
>>
>>
>
>


-- 

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________