From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX capacity exceeded - in Lua block - why?
Date: Thu, 16 Jul 2015 11:03:05 +0200 [thread overview]
Message-ID: <CAG5iGsAEX1nhPHgoNbE9KakbdFm-30ARq2SUvNy+tHpjGU6jPg@mail.gmail.com> (raw)
In-Reply-To: <op.x1uy2od0tpjj8f@lpr>
[-- Attachment #1.1: Type: text/plain, Size: 1651 bytes --]
On Thu, Jul 16, 2015 at 10:55 AM, Procházka Lukáš Ing. - Pontex s. r. o. <
LPr@pontex.cz> wrote:
> Hello,
>
> On Thu, 16 Jul 2015 10:27:48 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
> On 7/16/2015 10:20 AM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
>>
>>> Hello,
>>>
>>> why this code:
>>>
>>> ----
>>> \def\GG{\ifmmode G_G\else$\GG$\fi}
>>>
>>
>> because in math mode \GG expands \GG which expands \GG ....
>>
>
> I want to just pass G_G in math mode, so it seems to me that "\ifmmode
> G_G..." does the check.
>
> The macro should write G + "lower index G" for both math and non-math
> scope.
>
> And, in non math scope, the macro should just enclose itself by $...$ (or
> \m{...})...
>
> And, this works well in TeX code:
>
> ----
> \def\GG{\ifmmode G_G\else$\GG$\fi}
>
> \starttext
> \GG $\GG$
> \startitemize[][]
> \sym{\GG} \GG
> \sym{$\GG$} $\GG$
> \sym{\m{\GG}} \m{\GG}
> \item End
> \stopitemize
> \stoptext
> ----
>
> So how to rewrite the itemization into Lua?
>
> maybe you mean:
>>
>> \def\GG{\ifmmode G_G\else$GG$\fi}
>>
>
> ... Could be \def\GG{\ifmmode G_G\else$G_G$\fi}, too, but why not
> \def\GG{\ifmmode G_G\else$\GG$\fi} (seems to me be simpler as the macro
> definition - which may be more complicated - appears only once)?
>
>>
>>>
\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
but as soon as you fall into "mmod not true" then you have infinite
recursion.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 3279 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-07-16 9:03 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 [this message]
2015-07-16 10:13 ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-07-16 10:45 ` Hans Hagen
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=CAG5iGsAEX1nhPHgoNbE9KakbdFm-30ARq2SUvNy+tHpjGU6jPg@mail.gmail.com \
--to=luigi.scarso@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).