From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Testing non-existent counter in Lua
Date: Tue, 22 Jun 2010 08:35:01 +0200 [thread overview]
Message-ID: <4C205995.5050601@gyza.cz> (raw)
In-Reply-To: <4C205053.1060803@elvenkind.com>
Thanx Taco,
can I learn about these things somewhere read more? I tried
luatexref-t.pdf and I didnt in fact guided.
Thanx Jaroslav
Dne 22.6.2010 7:55, Taco Hoekwater napsal(a):
> Jaroslav Hajtmar wrote:
>> Hi, all.
>>
>> How do I know (due Lua) that the counter has not been defined in
>> ConTeXt (through the command newcount)?
>>
>> I am trying testing :
>>
>> if tex.count.mycount == nil then...
>>
>> or
>>
>> if tex.count.mycount == 'error' then...
>>
>> then when counter isnt defined due \newcount\mycount, then test
>> ending with error message.
>>
>> When counter is defined due
>> \newcount\mycount,
>> \mycount=1
>>
>> then test
>> if tex.count.mycount == 1 then...
>
> if token.command_name(token.create('mycount')) == 'assign_int'
> and tex.count.mycount == 1 then
> ...
> end
>
> Best wishes,
> Taco
>
>
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-06-22 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 21:41 Jaroslav Hajtmar
2010-06-22 5:55 ` Taco Hoekwater
2010-06-22 6:35 ` Jaroslav Hajtmar [this message]
2010-06-22 8:39 ` Taco Hoekwater
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=4C205995.5050601@gyza.cz \
--to=hajtmar@gyza.cz \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).