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