ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \startluacode and macro names with underscores
Date: Tue, 4 Sep 2012 15:48:26 +0200	[thread overview]
Message-ID: <52C3A212-0B79-4D75-869B-0B6E9A206965@gmail.com> (raw)
In-Reply-To: <20120904154025.4852eb9a@homerow>


Am 04.09.2012 um 15:40 schrieb Marco Patzer <homerow@lavabit.com>:

> Hi,
> 
> the luacode environment chokes on macro names with underscores.
> Example:
> 
> \starttext
> \unprotect
> 
> \def\number_two{two}
> 
> \startluacode
>  userdata = userdata or { }
>  function userdata.number_one() context("one") end
> 
>  -- works
>  userdata.number_one()
> 
>  -- fails
>  -- context.number_two()
> 
>  -- workaround
>  tex.print("\\number_two")
> \stopluacode
> 
> \protect
> \stoptext
> 
> Why is that and what can be done to access underscored macros in the
> usual way? I guess it's some catcode change from the function that
> prints into the TeX stream.


Use this in your Lua code:

context.unprotect()
context.number_two()
context.protect()

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-09-04 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 13:40 Marco Patzer
2012-09-04 13:48 ` Wolfgang Schuster [this message]
2012-09-04 13:49 ` Hans Hagen

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=52C3A212-0B79-4D75-869B-0B6E9A206965@gmail.com \
    --to=wolfgang.schuster@gmail.com \
    --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).