From: Vincent Hennebert via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Vincent Hennebert <vhennebert@gmail.com>
Subject: Re: Rendering Standalone MetaPost Graphics with ConTeXt
Date: Thu, 19 May 2022 18:22:21 +0200 [thread overview]
Message-ID: <e311b3dbf9e1a1cdbf5987f648a5c0aeba3c9632.camel@gmail.com> (raw)
In-Reply-To: <5568811.DvuYhMxLoT@sreeramtplt>
On Thu, 2022-05-19 at 14:23 +0530, śrīrāma wrote:
> On 5/19/22 1:53 PM Vincent Hennebert via ntg-context wrote:
> > Looking at the wiki, it seems that \startMPinclusions is not meant
> > to
> > actually render any content, just to include MetaPost code like
> > function definitions. I guess I would have expected \startMPpage
> > instead.
> >
> > Am I doing something wrong, or is that an error in ConTeXt?
>
> The MP statements should be inside a beginfig() .. endfig.
Oh, I see. Not super fan of enclosing each and every of my graphics in
a beginfig...endfig statement, but it does the job indeed.
Although in my case I must give a number parameter to beginfig,
otherwise I get an error.
Thanks Sreeram!
Vincent
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-05-19 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 8:23 Vincent Hennebert via ntg-context
2022-05-19 8:53 ` śrīrāma via ntg-context
2022-05-19 16:22 ` Vincent Hennebert via ntg-context [this message]
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=e311b3dbf9e1a1cdbf5987f648a5c0aeba3c9632.camel@gmail.com \
--to=ntg-context@ntg.nl \
--cc=vhennebert@gmail.com \
/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).