From: Alexandre Christe via ntg-context <ntg-context@ntg.nl>
To: Gavin <gavinpublic@comcast.net>
Cc: Alexandre Christe <aleks.christe@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MP figure continuation
Date: Fri, 6 Jan 2023 16:02:05 +0100 [thread overview]
Message-ID: <CALC5-UKprK_EgT=Z=x7+YXJ+r=BFKbs9H0wQ7CK+V4ms5vfavA@mail.gmail.com> (raw)
In-Reply-To: <5A42A919-6A4A-4377-971A-46C6AB06B1AD@comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]
Aye, thanks Mikael and Gavin. Hard 2023 re-start...
Le ven. 6 janv. 2023 à 15:58, Gavin <gavinpublic@comcast.net> a écrit :
> Hi Alex,
>
> > Is there a way to "continue" an MP figure? Like keeping the axes, etc.
> and just adding code to the figure?
>
> Buffers might be what you want. From the MetaFun manual:
>
> > Buffers can be used to stepwise build graphics. By putting code in
> multiple buffers, you can selectively process this code. [p.124]
>
> http://www.pragma-ade.nl/general/manuals/metafun-p.pdf
>
> Hope that helps.
>
> Gavin
[-- Attachment #1.2: Type: text/html, Size: 1026 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-06 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:43 Alexandre Christe via ntg-context
2023-01-06 14:53 ` Mikael Sundqvist via ntg-context
2023-01-06 14:58 ` Gavin via ntg-context
2023-01-06 15:02 ` Alexandre Christe via ntg-context [this message]
2023-01-07 2:35 ` Alan Braslau via ntg-context
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='CALC5-UKprK_EgT=Z=x7+YXJ+r=BFKbs9H0wQ7CK+V4ms5vfavA@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=aleks.christe@gmail.com \
--cc=gavinpublic@comcast.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).