From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use tex.print in ctxlua
Date: Sun, 19 Mar 2017 17:42:51 +0100 [thread overview]
Message-ID: <855AE2A2-6A82-46B8-89F8-8EC622887225@gmail.com> (raw)
In-Reply-To: <38578022-f4f0-40d1-2352-cad07940191d@gmx.es>
Hi Pablo,
Thanks for your answer: actually I did not know that it is possible to concatenate so easily in lua… Your solution is indeed simpler than what I did and solves also the problem of the spurious space before the closing parenthesis.
Best regards: OK
> On 19 Mar 2017, at 16:56, Pablo Rodriguez <oinos@gmx.es> wrote:
>
> On 03/19/2017 04:30 PM, Otared Kavian wrote:
>> Hi,
>>
>> I would like to print in a text the values of a array computed in a
>> \startluacode …. \stopluacode combination.
>> How can I do it properly? Please have a look at the example below
>> and its output, which is not satisfactory because the right parenthesis is
>> separated from the number by a space. How can I suppress this unwanted
>> space?
>> For instance I get (1, 103 ) instead of (1, 103).
>
> Hi Otared,
>
> is there any reason not to use the following instead of your way below?
>
> for i = 1,n do
> tex.print("(" .. vecteurX[i] .. ", " .. vecteurY[i] .. ")\\par")
> end
>
>> for i = 1,n do
>> context("(")
>> tex.print(vecteurX[i])
>> context(", ")
>> tex.print(vecteurY[i])
>> tex.print(")")
>> context.par()
>> end
>
> I think this is shorter and clearer (to me, at least).
>
> Just in case it helps,
>
> Pablo
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> 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:[~2017-03-19 16:42 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 [this message]
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
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=855AE2A2-6A82-46B8-89F8-8EC622887225@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).