ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: startMPgraphic?
Date: Mon, 31 Jan 2011 15:14:37 +0100	[thread overview]
Message-ID: <61A4A514-C852-4B3D-9FE2-2A842E80F726@uva.nl> (raw)
In-Reply-To: <41072931-A8B6-488B-8DD8-C1A277BBF2AD@uva.nl>

Some further digging brings to ligt that my metapost files cannot be found by the luatex run.
The following is hown in the log:

mplib           : initializing instance 'metafun' using format 'metafun'
mplib           : loading 'metafun.mp' (experimental metapost version two)
mplib           > mp terminal: ! I can't open file `hvdm'.
<*> ...core : input mp-core.mp ; fi ; ;\input hvdm
                                                   def init_pens = pickup pe...
Please type another input file name

Now that is strange, because looking into the ls-R in texmf-local I see them present:

./tex/context/user/metapost:
.DS_Store
.svn
hvdm.mp
mygraph.mp

So, why is hvdm.mp not found? Other files mentioned in ls-R, for example:
./tex/context/user/context-user:
hvdm-cas.tex
hvdm-dvd.tex
etcetera, are indeed found.

By the way, why are all the .svn (subversion) directories included in ls-R? Cannot .svn/* be excluded? 

Hans van der Meer


 
On 31 jan 2011, at 14:08, Hans van der Meer wrote:

> I just started the conversion of my presentation sheets to ConTeXt mkIV. As could be expected, some inconsistencies will turn up. However this one escapes me. What I am missing that
>   \startMPgraphic
> results in
>   ! Undefined control sequence.
> 
> I thought that installing the minimals of ConTeXt-beta also installed the metafun module. Or has this one macro been deprecated?
> 
> Hans van der Meer
> 
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________


  reply	other threads:[~2011-01-31 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 13:08 startMPgraphic? Hans van der Meer
2011-01-31 14:14 ` Hans van der Meer [this message]
2011-01-31 15:17   ` startMPgraphic? Hans Hagen
2011-01-31 16:51   ` startMPgraphic? Aditya Mahajan

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=61A4A514-C852-4B3D-9FE2-2A842E80F726@uva.nl \
    --to=h.vandermeer@uva.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).