ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using lua to define a macro with one optional parameter in brackets
Date: Wed, 08 Jul 2015 16:11:34 +0200	[thread overview]
Message-ID: <559D2F96.9000001@gyza.cz> (raw)
In-Reply-To: <A363800A-0ADE-4FCD-B337-AD1F2B2B16FF@elvenkind.com>

Thanks Taco very much.

At this point, it really works in simple situations, but in the event 
that this solution will incorporate into the existing system, then I 
have big problems with expansion (values are not updated in macros). I 
need more solutions using something like context.setgvalue, or at least 
according to the following example. If they could incorporate the 
remaining two definitions
ie
\def\simpleA {content when parameter is missing}
\def\complexA[#1]{parameter #1}

into luacode (probably encounter a problem with #), so it might work. 
Can not think of anyone, how it could be done differently?
Thanks Jaroslav Hajtmar

Here is minimal example:

\ctxlua{
xlsname='A'
content='content when parameter is missing'
context([[\definecomplexorsimple\]]..xlsname)
%context([[\def\simple]]..xlsname..[[{]]..content..[[}]])
%context([[\def\complex]]..xlsname..'[#1]'..[[{Neco: #1}]])
}

\def\simpleA {content when parameter is missing}
\def\complexA[#1]{parameter #1}



\type{\A}: \A

\type{\A[5]}: \A[5]


\stoptext




Dne 8. 7. 2015 v 14:11 Taco Hoekwater napsal(a):
>> On 08 Jul 2015, at 13:58, Jaroslav Hajtmar <hajtmar@gyza.cz> wrote:
>>
>> Thanx Taco for reply.
>>
>> the minimal example see bellow not crashed, but \A macro is not created.
>> I don't Know in what could still be a problem. Example I am even more minimalize
> It works for me after changing \directlua {} to \startluacode … \stopluacode
>
> Best wishes,
> Taco
>
>
>
>

___________________________________________________________________________________
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:[~2015-07-08 14:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08  9:05 Jaroslav Hajtmar
2015-07-08 10:07 ` Taco Hoekwater
2015-07-08 10:40   ` Jaroslav Hajtmar
2015-07-08 11:04   ` Jaroslav Hajtmar
2015-07-08 11:28     ` Taco Hoekwater
2015-07-08 11:58       ` Jaroslav Hajtmar
2015-07-08 12:11         ` Taco Hoekwater
2015-07-08 14:11           ` Jaroslav Hajtmar [this message]
2015-07-08 18:54             ` Hans Hagen
2015-07-09  5:22               ` Jaroslav Hajtmar
2015-07-09  7:25                 ` Taco Hoekwater
2015-07-09  9:07                 ` Hans Hagen
2015-07-09 15:05                   ` Jaroslav Hajtmar
2015-07-09 15:24                     ` Hans Hagen
2015-07-10 20:40                       ` Jaroslav Hajtmar
2015-07-13 13:04 Jaroslav Hajtmar
2015-07-13 14:14 ` 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=559D2F96.9000001@gyza.cz \
    --to=hajtmar@gyza.cz \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).