ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@bittext.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Own command definition breaks with interaction: Use of \do_my_command doesn't match its definition
Date: Mon, 29 Jan 2024 09:30:08 +0100	[thread overview]
Message-ID: <34DC5532-70A0-40E5-8275-0C2BE2E81E35@bittext.nl> (raw)
In-Reply-To: <2780043.ElGaqSPkdT@falbala>

Hi,

You can try: 

> \unexpanded\def\do_my_command[#1]#2{%

But there is probably a cleaner way to implement optional arguments with lua?

Best wishes,
Taco

> On 25 Jan 2024, at 09:18, Gerion Entrup <gerion.entrup@flump.de> wrote:
> 
> Hi,
> 
> I want to make a proper definition of a new command to be able to
> process it in Lua. I found something on StackOverflow [1] but that
> breaks in enumeration _and_ when interaction is enabled and I do not
> understand why? Can you give me some help here?
> 
> I want to make commands like \foo{bla} and \foo[b]{bla} possible at the
> same time. Here is a minimal example (also attached):
> 
> ```
> \startluacode
> function userdata.my_command(keywords, text)
> commands.writestatus("test", string.format("text: %s, config: %s", text, keywords))
>    local cfg = utilities.parsers.settings_to_hash(keywords)
> 
> if cfg['emph'] ~= nil then
> context("\\emph{" .. text .. "}")
> elseif cfg['bold'] ~= nil then
> context("\\bold{" .. text .. "}")
> else
> context(text)
> end
> end
> \stopluacode
> 
> % without that line there is no problem
> \setupinteraction[state=start]
> 
> \defineenumeration[enu][text=Enu]
> 
> \unprotect
> \def\mc{\dosingleempty\do_my_command}
> \def\do_my_command[#1]#2{%
> \iffirstargument{%
> \ctxlua{userdata.my_command('#1', [==[#2]==])}%
> }\else {%
> \ctxlua{userdata.my_command('', [==[#2]==])}%
> }\fi
> }
> \protect
> 
> \starttext
> 
> % all the following works
> \mc{foo} \mc[bold]{foo} \mc[emph]{foo}
> 
> \startenu[title=Some]
> \stopenu
> 
> % this breaks
> \startenu[title=Some \mc{foo}]
> \stopenu
> 
> \stoptext
> ```
> 
> The compilation fails with:
> ```
> tex error       > tex error on line 41 in file ./test.tex: Use of \do_my_command doesn't match its definition
> ```
> 
> Best,
> Gerion
> 
> [1] https://tex.stackexchange.com/a/55778
> <test.tex>___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive  : https://github.com/contextgarden/context
> wiki     : https://wiki.contextgarden.net
> ___________________________________________________________________________________

— 
Taco Hoekwater              E: taco@bittext.nl
genderfluid (all pronouns)


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-01-29  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  8:18 [NTG-context] " Gerion Entrup
2024-01-29  8:30 ` Taco Hoekwater [this message]
2024-01-29 15:31 ` [NTG-context] " Wolfgang Schuster

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=34DC5532-70A0-40E5-8275-0C2BE2E81E35@bittext.nl \
    --to=taco@bittext.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).