ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Jeong Dal <haksan@me.com>
Subject: Re: new (lmtx) beta
Date: Fri, 11 Oct 2019 17:09:58 +0200	[thread overview]
Message-ID: <e061d945-1c85-ec5c-ebd8-90f7e55020b5@xs4all.nl> (raw)
In-Reply-To: <CD0FA539-B3D7-4144-BF14-582762610BE8@me.com>

On 10/11/2019 4:09 PM, Jeong Dal wrote:
> 
> Dear Hans,
> 
> I read the manual of luametafun and do some examples.
> Thanks for many new features.
> It is  really great.
> 
> I’d like to ask two things.
> 
> 1. On  page 26,27, in the manual,
>>
>> http://www.pragma-ade.com/general/manuals/luametafun.pdf
> 
> a function name of the graphics are appeared as same as in the argument 
> ‘function = “x^2 + y^2”’.
> Though it calculates function using “x^2 + y^2”,  it is better to write 
> the name of it as the output of $x^2 + y^2$.
> Is it possible to write  it as in mathematical form?

         functionstyle = "math",


> 2. To define a mathematical function, it uses “function = “ in Contour, 
> while it uses “code = “ in Surfaces and in Functions.
> Is there any reason to use two different names “function” and “code” to 
> define functions?
we can still decide as it's beta ...

   function | functions

or

   code | codelist

(it's basically lua code ...)

i have no preference and as you're the first to bring it up you may 
decide ... (unless others can convince you otherwise)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-10-11 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1570356001.2603.ntg-context@ntg.nl>
2019-10-11 14:09 ` Jeong Dal
2019-10-11 15:09   ` Hans Hagen [this message]
2019-10-11 22:19     ` Jeong Dal
2020-01-26 18:38 new lmtx beta Hans Hagen
2020-01-26 18:40 ` Mojca Miklavec
2020-01-26 19:16   ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2019-10-04 16:10 new (lmtx) beta Hans Hagen
2019-10-04 19:33 ` Mikael P. Sundqvist
2019-10-05  7:39   ` Fabrice Couvreur
2019-10-05  7:45     ` Wolfgang Schuster
2019-10-05 10:52       ` Mikael P. Sundqvist
2019-10-06  8:39         ` Fabrice Couvreur

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=e061d945-1c85-ec5c-ebd8-90f7e55020b5@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=haksan@me.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).