From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use tex.print in ctxlua
Date: Sun, 19 Mar 2017 18:26:49 +0100 [thread overview]
Message-ID: <928a2077-e54a-dec9-e30f-801dada95484@wxs.nl> (raw)
In-Reply-To: <58CEB849.1020003@gmail.com>
On 3/19/2017 5:56 PM, Wolfgang Schuster wrote:
>
>> Otared Kavian <mailto:otared@gmail.com>
>> 19. März 2017 um 17:46via Postbox
>> <https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach>
>> Hi Aditya,
>>
>> Thanks, as Thomas, Pablo and you mentioned the right way is to use
>> context() instead of tex.print()
>> Actually I just saw that one can also concatenate with context() as in:
>>
>> context("(" .. vecteurX[i] .. ", " .. vecteurY[i] .. ")\\par")
>>
>> which is equivalent to
>> tex.print("(" .. vecteurX[i] .. ", " .. vecteurY[i] .. ")\\par")
> You can use the string.formatters function for this.
>
> \starttext
>
> \startluacode
>
> local string_a = "12"
> local string_b = "23"
>
> context(string.formatters["(%s,%s)"](string_a,string_b))
>
> \stopluacode
>
> \stoptext
\starttext
\startluacode
local string_a = "12"
local string_b = "23"
context("(%s,%s)",string_a,string_b)
context.formatted.bold("(%s,%s)",string_a,string_b)
\stopluacode
\stoptext
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2017-03-19 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 15:30 Otared Kavian
2017-03-19 15:39 ` josephcanedo
2017-03-19 15:51 ` Thomas A. Schmitz
2017-03-19 16:39 ` Otared Kavian
2017-03-19 17:28 ` Hans Hagen
2017-03-19 15:56 ` Pablo Rodriguez
2017-03-19 16:42 ` Otared Kavian
2017-03-19 16:53 ` Thomas A. Schmitz
2017-03-19 16:37 ` Aditya Mahajan
2017-03-19 16:46 ` Otared Kavian
2017-03-19 16:56 ` Wolfgang Schuster
2017-03-19 17:17 ` Otared Kavian
2017-03-19 17:26 ` Hans Hagen [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=928a2077-e54a-dec9-e30f-801dada95484@wxs.nl \
--to=pragma@wxs.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).