From: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: FWD: \inmargin, \setupindenting, and overfull boxes
Date: Sat, 07 May 2005 15:47:16 +0200 [thread overview]
Message-ID: <427CC6E4.4060102@elvenkind.com> (raw)
In-Reply-To: <42B10CBE@webmail.colostate.edu>
Idris Samawi Hamid wrote:
> I placed your definition in a \start-\stopenvironment file. The \inmargins are
> in \product files each of which calls the environment file in its preamble. If
> I compile just one product (say the second \product from the project), there
> appears to be no problem. But if I compile the entire project, TeX chokes on
> that same product.
>
> Do you think this may be the problem?
Yes, because the environment file is read twice, you need a guard against redefining the redefinition. Placing a guard around it, like this, should work:
\expandafter\ifx\csname normalinmargin \endcsname \relax \else
\let\normalinmargin\inmargin
\def\inmargin#1{{\parindent0pt \normalinmargin{#1}}}
\fi
(yes, that is an ugly hack, but it is one I can write withour actually having to test it before sending :))
Greetings, Taco
next prev parent reply other threads:[~2005-05-07 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 13:30 Idris Samawi Hamid
2005-05-07 13:47 ` Taco Hoekwater [this message]
-- 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 2:55 Idris Samawi Hamid
2005-05-07 9:14 ` 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=427CC6E4.4060102@elvenkind.com \
--to=taco@elvenkind.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).