ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX capacity exceeded - in Lua block - why?
Date: Thu, 16 Jul 2015 12:45:37 +0200	[thread overview]
Message-ID: <55A78B51.9070809@wxs.nl> (raw)
In-Reply-To: <op.x1u2o2futpjj8f@lpr>

On 7/16/2015 12:13 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
> Hello,
>
> On Thu, 16 Jul 2015 11:03:05 +0200, luigi scarso
> <luigi.scarso@gmail.com> wrote:
>
>>  \def\GG{\ifmmode G_G\else$\GG$\fi}
>> means "define the macro \GG as G_G if mmmod is true,
>> else as \GG "
>> It's clear that you  always are in a situation where mmod is true,
>> then \GG
>> is replaced with  G_G
>
> Well, I intended "replaced with $G_G$",
>               not "replaced with  G_G";
> so I thought this would force/ensure math mode and thus prevent infinite
> recursion.
>
>> but as soon as you fall into "mmod not true" then you have infinite
>> recursion.
>
> Also, my observation was that my original macro worked well when called
> for TeX code (at various places of use:
>    \GG $\GG$
>    \startitemize[][]
>      \sym{\GG} \GG
>      \sym{$\GG$} $\GG$
>      \sym{\m{\GG}} \m{\GG}
>      \item End
>    \stopitemize
> )
> but stopped working when called from Lua (?!).

it all depends ... if you pass it in a way that it gets expanded you get 
already expansion at the write

you could try \unexpanded\def\GG then

it's hard to say what happens unless one sees the whole application (for 
which i have no time anyway)


> @Hans:
>
> This seems to be best solution - exactly what I wanted to achieve:
> \def\GG{\mathematics{G_G}}.
>
> Thanks both for your help.
>
> Best ragrds,
>
> Lukas
>
>


-- 

-----------------------------------------------------------------
                                           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:[~2015-07-16 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:20 Procházka Lukáš Ing. - Pontex s. r. o.
2015-07-16  8:27 ` Hans Hagen
2015-07-16  8:55   ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-07-16  9:03     ` luigi scarso
2015-07-16 10:13       ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-07-16 10:45         ` Hans Hagen [this message]
2015-07-16 10:52         ` Hans Hagen
2015-07-16 13:29         ` luigi scarso
2015-07-16  9:29     ` 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=55A78B51.9070809@wxs.nl \
    --to=pragma@wxs.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).