From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: document structure (small bug)
Date: Sat, 22 Jul 2006 14:19:28 +0200 [thread overview]
Message-ID: <44C217D0.8000208@elvenkind.com> (raw)
In-Reply-To: <28439B97-4AB7-4F5D-A1C3-019A18D09DE7@science.uva.nl>
Hi Hans-es,
Hans van der Meer wrote:
>
>
> No, I must be my fault, but even with the above help I cannot get it
> working.
> As far as I can figure out the value of \currentproduct seems NOT to
> guard entry to the body of \startlocalenvironment[syllabus-s].
This took a bit of digging, it appears to be a bug in core-job.tex.
The definition of \setvalue{\e!start\v!localenvironment} ends with:
{\grabuntil{\e!stop\v!localenvironment}\relax}}
but that should be:
{\grabuntil{\e!stop\v!localenvironment}\gobbleoneargument}}
> Also \localenvironment seems to accept any
> file for reading instead of rejecting everything except the current
> product/component.
Yes, it only guards against loading the environment file twice. The
name is irrelevant.
> In the code of core-job.tex I read:
>
> % more or less replaced by modes
> \setvalue{\e!start\v!localenvironment}[#1]%
> ....
>
> Must I conclude from this that localenvironments are more or less
> passe? So that I can better avoid them and use modes (after
> \enablemode) as discriminating criterium?
There are probably system modes predefined for the products
name etc. I'll leave the question to be answered by Hans.
Taco
next prev parent reply other threads:[~2006-07-22 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 10:20 document structure Hans van der Meer
2006-07-21 12:58 ` Taco Hoekwater
2006-07-21 18:02 ` Hans van der Meer
2006-07-22 8:19 ` Taco Hoekwater
2006-07-22 11:38 ` Hans van der Meer
2006-07-22 12:19 ` Taco Hoekwater [this message]
2006-07-22 12:40 ` document structure (small bug) Hans van der Meer
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=44C217D0.8000208@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).