From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: ntg-context@ntg.nl
Subject: Re: Last version standalone ConTeXt issue.
Date: Tue, 9 Feb 2016 20:37:45 +0100 [thread overview]
Message-ID: <56BA4009.4040907@gyza.cz> (raw)
In-Reply-To: <56BA3508.2060703@wxs.nl>
Thanx Hans.
Great! It works fine now! For me it is very useful and important macro.
One more thanx for reply.
Jaroslav Hajtmar
Dne 09.02.16 v 19:50 Hans Hagen napsal(a):
> On 2/9/2016 1:28 PM, Jaroslav Hajtmar wrote:
>> Hello ConTeXist.
>>
>> In the latest version ConTeXt it stopped working my macros which
>> contents function he once advised me Taco. It is low level lua code.
>> Can anyone advise me what the problem is, eventually. how to replace Lua
>> code in my function to make it work again? Macros worked at least 6
>> years and now crashes.
>>
>> Here is my function:
>>
>> function thirddata.handlecsv.texmacroisdefined(macroname) -- check
>> whether macroname macro is defined in ConTeXt
>> -- function is used to test whether the user has defined the macro
>> \macroname. If not, it needs to define any default value
>> if token.csname_name(token.create(macroname)) == macroname then
>> return true
>> else
>> return false
>> end
>> end
>>
>> Is there any alternative (ConTeXt like), which is should be possible use
>> in Lua code?
>
> \starttext
>
> \startluacode
>
> function interfaces.defined(name)
> return token.get_cmdname(token.create(name)) ~= "undefined_cs"
> end
>
> if interfaces.defined("foo") then
> context("foo")
> else
> interfaces.setmacro("foo","bar")
> end
>
> \stopluacode
>
> \foo
>
> \stoptext
>
> I'll add interfaces.defined to the core.
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.com | 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://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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-02-09 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 12:28 Jaroslav Hajtmar
2016-02-09 18:50 ` Hans Hagen
2016-02-09 19:37 ` Jaroslav Hajtmar [this message]
2016-10-10 9:48 ` Meer, Hans van der
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=56BA4009.4040907@gyza.cz \
--to=hajtmar@gyza.cz \
--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).