ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: hajtmar@gyza.cz, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Optimal way to defining of macros in Luacode in ConTeXt
Date: Wed, 13 Jul 2011 11:55:33 +0200	[thread overview]
Message-ID: <4E1D6B95.4080200@wxs.nl> (raw)
In-Reply-To: <4E1D51D5.50507@gyza.cz>

On 13-7-2011 10:05, Jaroslav Hajtmar wrote:
> Hello all.
> It is GREAT! Thanx Hans and Wolfgang too. It is very instructive and
> inspiring for me...
> I was looking for something similar for a long time, but I have not
> found anything (not even in the CLD-MKIV and others ...). Finally, after
> yours reply to this email find something in the ctx-man.pdf from 1997
> year :-).
> But I have a few questions and comments on this subject:
>
> 1. Is there any possibility to do anything similar with counters,
> dimensions etc? I trying but without success.
> For example:
> context.newcount(mycounter) or context.newcounter(mycounter)
> context.mycounter=5 etc.

As currently we cannot define a counter at the tex end (using countdef) 
it would introduce too much complexitity to mimmick that now.

When you do:

context.newcount("name")

you should realize that this command is effectuated after the lua call, 
so if you want a counter also at the tex level you should define it at 
that end,

\newcount\name

> or it must be realized by classical way:
> context('\\newcount\\mycounter')
> context('\\mycounter=10')
> context('\\advance\\mycounter by5')
> context('\\the\\mycounter')

tex.count.name = 10
tex.count.name = tex.count.name + 5

if you never need the counter at the tex end, you can of course use a 
lua number instead.

> similary with \newdimen, \newif etc...

at some point we will have helpers for that

> 2. Any person interested in using context.setvalue{"Mymacro",somevalue)
> and context([[\def\MyMacro#1{#1}]]) syntaxes I have pointed out that the
> second syntax only operates when the command is given in a separate LUA
> file (ie file.lua) (ie not within an environment \startluacode -
> \stopluacode in classical TEX file!!!). Hans told me once that it is the
> individual categories of characters (backslash??) (if I remember
> correctly).
> First syntax works perfectly in LUA and TeX files too.

indeed, but if you already have the command and it's defined as 
unexpandable then you can use the [[ ]] method too

> Here I have a question. Why not comment out this case in TEX file?
>
> \startluacode
> -- context([[\def\macro#1{#1}]])
> \stopluacode
>
> I get error:
> ! Undefined control sequence.
> -- context([[\def \macro
> #1{#1}]])
> \dodostartluacode ...and \directlua \zerocount {#1
> }}
> l.25 \stopluacode
> ?
>
> That category characters again? Comment character -- works differently
> in TEX file, and otherwise in the LUA file?
> Ie. comment on the backslash?

indeed

> 3. Wolfgang write about using context command
>
> \convertnumber{R}{1400} and the corresponding syntax:
> context.convertnumber("R",1400) to roman converting.
> It is great, but I could not figure out how to use in combination with
> the above syntax (ie use case context.command) or find the appropriate
> conversion LUA function (I did not use a custom function).
> Is there any way to do something like that:
>
> context([[\def\Macro%s{Macro%s}]],context.convertnumber("R",1400),1400) ???
> ie. TEX command is used as a LuaTeX parameter?

context([[\def\Macro%s{Macro%s}]],converters.romannumeral(1400),1400)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________


  reply	other threads:[~2011-07-13  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 15:30 Jaroslav Hajtmar
2011-07-12 15:43 ` Hans Hagen
2011-07-13  8:05   ` Jaroslav Hajtmar
2011-07-13  9:55     ` Hans Hagen [this message]
2011-07-13 10:05       ` Jaroslav Hajtmar
2011-07-13 12:56         ` Wolfgang Schuster
2011-07-13 14:09           ` Jaroslav Hajtmar
2011-07-13 14:33             ` Wolfgang Schuster
2011-07-14 15:12               ` Jaroslav Hajtmar
2011-07-14 15:28                 ` Hans Hagen
2011-07-13 18:05             ` Hans Hagen
2011-07-12 15:50 ` 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=4E1D6B95.4080200@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=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).