From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: metafun 2
Date: Sun, 8 Sep 2019 12:09:00 +0200 [thread overview]
Message-ID: <CC286DBB-5CEF-421A-9A51-8046BDBF8304@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.76.1909080439280.1621@nqv-guvaxcnq>
Hi Aditya,
As usual you show us a very nice and very clear example to taech nice features of ConTeXt: thank you so much!
I wanted also to point out a typo on that page (two occurrences), namely "ploles" instead of "poles", in the explanations before the actual code.
Best regard:
> On 8 Sep 2019, at 10:42, Aditya Mahajan <adityam@umich.edu> wrote:
>
> On Wed, 14 Aug 2019, Hans Hagen wrote:
>
>> Hi,
>>
>> In the process of providing an additional (more abstract) interface to some of the old and also new MetaFun code we wonder what kind of features users would like to see.
>>
>> http://www.pragma-ade.com/general/magazines/mag-1104-mkiv.pdf
>
> Finally got around to playing around with the new interface. Here is an example of how to define new key-value driven macros in metapost:
>
> https://adityam.github.io/context-blog/post/new-metafun-interface/
>
> Aditya
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-09-08 10:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 9:54 Hans Hagen
2019-08-14 10:18 ` Henri Menke
2019-08-14 11:16 ` Hans Hagen
2019-08-14 11:31 ` Floris van Manen
2019-08-14 11:53 ` Hans Hagen
2019-08-15 6:05 ` Arthur Reutenauer
2019-08-14 14:22 ` Otared Kavian
2019-08-14 14:49 ` Hans Hagen
2019-08-14 14:53 ` Aditya Mahajan
2019-08-14 14:58 ` Otared Kavian
2019-08-14 15:11 ` Wolfgang Schuster
2019-08-14 15:34 ` Hans Hagen
2019-08-14 14:58 ` Mikael P. Sundqvist
2019-08-14 15:37 ` Hans Hagen
[not found] ` <CAHy-LL9D5NB6qZYj+QynCWR-rqk6suD3reepLUgO8KOwrjwnXA@mail.gmail.com>
2019-08-19 19:20 ` Fwd: " Mikael P. Sundqvist
2019-08-16 23:31 ` Adam Reviczky
2019-08-17 1:27 ` Alan Braslau
2019-08-17 8:52 ` Hans Hagen
2019-08-17 18:12 ` Adam Reviczky
2019-08-19 19:15 ` Jorge Manuel
2019-09-08 8:42 ` Aditya Mahajan
2019-09-08 10:09 ` Otared Kavian [this message]
2019-09-08 14:54 ` 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=CC286DBB-5CEF-421A-9A51-8046BDBF8304@gmail.com \
--to=otared@gmail.com \
--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).