ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: unprotecting when defining in Lua
Date: Mon, 29 Apr 2024 18:04:55 +0200	[thread overview]
Message-ID: <b6b65432-877b-20bf-78e9-94379a6b7b99@gmail.com> (raw)
In-Reply-To: <3950da22-fd1e-6cd7-23e8-fca463fcd96c@gmx.es>

Pablo Rodriguez via ntg-context schrieb am 29.04.2024 um 17:22:
> Dear list,
>
> I have the following sample:
>
>    \starttext
>    \startluacode
>      function document.test(str)
>        context(str)
>      end
>
>      interfaces.definecommand {
>        name = "testing",
>        protected = false,
>        macro = document.test,
>      }
>    \stopluacode
>
>    \meaningfull\testing
>
>    \def\test#1{#1}
>
>    \meaningfull\test
>    \stoptext
>
> Which is the right way to use "interfaces.definecommand" to get a simple
> command as in standard TeX?
>
> I mean, no a non \permanent or non \protected command.

You can't create unprotected command with interfaces.definecommand but 
this not a problem
because you can just use interfaces.implement to create your command 
which is then unprotected
by default. Using implement instead of definecommand doesn't matter 
because definecommand
is just a wrapper for the implement function with the option to create a 
environment.

Wolfgang

___________________________________________________________________________________
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-04-29 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 15:22 [NTG-context] " Pablo Rodriguez via ntg-context
2024-04-29 16:04 ` Wolfgang Schuster [this message]
2024-04-29 16:21   ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-04-29 17:32     ` Wolfgang Schuster
2024-04-29 18:21       ` Pablo Rodriguez via ntg-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=b6b65432-877b-20bf-78e9-94379a6b7b99@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).