From: Hans van der Meer <havdmeer@ziggo.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: Checking existence of a macro (control sequence) by Lua - problem after updating MkIV
Date: Thu, 18 Jun 2020 12:21:49 +0200 [thread overview]
Message-ID: <4A610884-7395-45B9-9D92-DF0409B440F2@ziggo.nl> (raw)
In-Reply-To: <aKZ.6Ap99.6My3xehTF99.1UwoLs@seznam.cz>
[-- Attachment #1.1: Type: text/plain, Size: 2259 bytes --]
Why can you not simply use one of the doifundefined macro's? Something for example:
\doifundefined{ExitStatus}{\gdef\ExitStatus{0}} % default to ok as in UNIX
dr. Hans van der Meer
> On 18 Jun 2020, at 10:27, Lukas/ConTeXt <lpr.context@email.cz> wrote:
>
> Hello,
> I'm using Hans' macro suggested some time before.
> I've just updated Ctx MkIV and my sample code:
>
> ----
> \starttext
> \def\MyMacro{Ahoj}
>
> \def\MyMacWithPars#1#2{Something}
>
> \def\Undefined{}
> \let\Undefined\undefined
>
> \def\DoNothing{}
> \let\DoNothing\donothing
>
> \startluacode
> if CONTEXTLMTXMODE == 0 then
> local d = tokens.defined
> local c = tokens.create
>
> function tokens.defined(s,b)
> if b then
> return d(s)
> else
> return c(s).cmd_name == "undefined_cmd"
> end
> end
> end
>
> --
>
> local defined = tokens.defined
>
> for _, v in ipairs{ "MyMacro", "MyMacWithPars", "Undefined", "DoNothing", "NonExisting" } do
> print(string.format("\letterpercent-12s", v), defined(v), defined(v, true), defined(v, false))
> end
> \stopluacode
>
> Aaa
> \stoptext
> ----
>
> gives:
> "
> MyMacro false false false
> MyMacWithPars false false false
> Undefined false false false
> DoNothing false false false
> NonExisting false false false
> "
>
> IOW, I'm not able to determine whether a control sequence has not been defined (or has \undefined value) or not.
>
> Am I doing a trivial mistake or has anything changed?
>
> Thank you for patience...
>
> Lukas<IsMacDef3.log><IsMacDef3.mkiv><IsMacDef3.log_>___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 6058 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2020-06-18 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 8:27 Lukas/ConTeXt
2020-06-18 10:21 ` Hans van der Meer [this message]
2020-06-18 10:29 ` Lukas/ConTeXt
2020-06-18 20:52 ` Hans Hagen
2020-06-19 6:36 ` Lukas/ConTeXt
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=4A610884-7395-45B9-9D92-DF0409B440F2@ziggo.nl \
--to=havdmeer@ziggo.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).