From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: RE: FWD: \inmargin, \setupindenting, and overfull boxes
Date: Fri, 6 May 2005 20:55:17 -0600 [thread overview]
Message-ID: <42B05C4A@webmail.colostate.edu> (raw)
Hi Taco,
Ok your hack works for small files but in my larger work this is causing TeX's
capacity to overload (indeed, I don't think I've run into this particular
overload message before; does the `255' signify some ceiling here?):
=======================================================
! TeX capacity exceeded, sorry [grouping levels=255].
\normalinmargin #1->{
\parindent 0pt \normalinmargin {#1}}
\normalinmargin ...indent 0pt \normalinmargin {#1}
}
\normalinmargin ...indent 0pt \normalinmargin {#1}
}
\normalinmargin ...indent 0pt \normalinmargin {#1}
}
\normalinmargin ...indent 0pt \normalinmargin {#1}
}
\normalinmargin ...indent 0pt \normalinmargin {#1}
}
...
=====================================================
Although if I implement this manually it does not overload TeX:
===================================================
\setupoutput[pdftex]%
\setupindenting[medium]
%\let\normalinmargin\inmargin
%\def\inmargin#1{{\parindent0pt \normalinmargin{#1}}}
\starttext
\input knuth {\parindent0pt\inmargin{This is a test.}}
\stoptext
===================================================
Something about that pseudo-recursive definition I suppose? It may take a
while for me to narrow this new problem down to a small file, but I can
privately send you the larger files if you care to look at this.
Thnx 4 all your help.
Best
Idris
>===== Original Message From Taco Hoekwater <taco@elvenkind.com> =====
>Hi Idris,
>
>It's definately a \parindent, but I cannot figure whence it came.
>Anyway, if you need an immediate fix, the following hack works:
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-05-07 2:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 2:55 Idris Samawi Hamid [this message]
2005-05-07 9:14 ` Taco Hoekwater
-- strict thread matches above, loose matches on Subject: below --
2005-05-09 15:36 Idris Samawi Hamid
2005-05-08 21:36 Idris Samawi Hamid
2005-05-07 20:00 Idris Samawi Hamid
2005-05-08 20:04 ` Hans Hagen
2005-05-08 21:29 ` Taco Hoekwater
2005-05-09 9:49 ` Hans Hagen
2005-05-07 19:48 Idris Samawi Hamid
2005-05-07 14:21 Idris Samawi Hamid
2005-05-08 7:46 ` Taco Hoekwater
2005-05-07 13:30 Idris Samawi Hamid
2005-05-07 13:47 ` Taco Hoekwater
2005-04-27 2:18 Idris Samawi Hamid
2005-05-05 16:35 ` Fwd: " Idris Samawi Hamid
2005-05-06 6:46 ` Taco Hoekwater
2005-05-06 14:44 ` Idris Samawi Hamid
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=42B05C4A@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).