From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: left bracket in string.format()
Date: Mon, 26 Aug 2013 18:39:04 +0200 [thread overview]
Message-ID: <521B84A8.8000202@gmx.net> (raw)
In-Reply-To: <21CFE584-BFD9-4215-8760-4BDC07D5E071@gmail.com>
Am 26.08.2013 17:40, schrieb Wolfgang Schuster:
>
> Am 26.08.2013 um 17:01 schrieb Peter Rolf <indiego@gmx.net>:
>
>> Hi,
>>
>> Not sure if this is a bug or intended behaviour. I want to fill a TABLE
>> row with "[<number>]", but the leading left bracket causes some problems
>> here. I tried the syntax 'print(string.format("[%d]",10)' in pure lua
>> and the result is as desired.
>>
>> %% --------------
>> \starttext
>>
>> \startluacode
>> context.bTABLE{}
>> context.bTR()
>> for i = 1,8 do
>> context.bTH() context(string.format("[%d]",i)) context.eTH()
>> end
>> context.eTR()
>> context.eTABLE()
>> \stopluacode
>>
>> \stoptext
>> %% --------------
>>
>> gives
>>
>> [..]
>> fonts > 'fallback modern rm 12pt' is loaded
>> setup > error in line 6, namespace '354>', key '1'
>> setup > error in line 9, namespace '354>', key '2'
>> setup > error in line 12, namespace '354>', key '3'
>> setup > error in line 15, namespace '354>', key '4'
>> setup > error in line 18, namespace '354>', key '5'
>> setup > error in line 21, namespace '354>', key '6'
>> setup > error in line 24, namespace '354>', key '7'
>> setup > error in line 27, namespace '354>', key '8'
>> [..]
>>
>> and empty TABLE cells. Any help welcome.
>
> The \bTH command has a optional argument and when you print [<number>]
> context take this as argument for \bTH. There are different ways to fix this,
> one is to pass a empty argument to \bTH, e.g. "context.bTH{}" or you add \relax
> after the command, e.g. "context.bTH() context.relax()".
>
> BTW: You don’t need string.format because “context("[%d]",i)" is valid input.
>
Thanks Wolfgang for the detailed answer! :-)
> Wolfgang
>
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-08-26 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 15:01 Peter Rolf
2013-08-26 15:40 ` Wolfgang Schuster
2013-08-26 16:39 ` Peter Rolf [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=521B84A8.8000202@gmx.net \
--to=indiego@gmx.net \
--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).