From: Herbert Voss <Herbert.Voss@FU-Berlin.DE>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: itemize
Date: Tue, 19 Oct 2010 14:01:52 +0200 [thread overview]
Message-ID: <4CBD88B0.7060706@FU-Berlin.DE> (raw)
In-Reply-To: <4CBD780E.2020608@FU-Berlin.DE>
Am 19.10.2010 12:50, schrieb Herbert Voss:
> Am 19.10.2010 11:27, schrieb Hans Hagen:
>
>> If I remember right this is a bug in the luatex version that ships with
>> texlive.
>
> I updated from http://tlcontrib.metatex.org/2010
>
> and now it is ok
But only for a moment ... :-( But now I know
what happens.
The problem is that I run several context files
from a script. But the context sources are generated
before from within a LaTeX document. Before I run
this document with LaTeX I set TEXINPUTS to antother
value, but always with "...:$TEXINPUTS". After
running pdflatex the script then runs
all ConTeXt documents and it seems that the setting
of TEXINPUTS is not correct for the context runs.
When I do an "unset TEXINPUTS" inside the script
before running context on the files everything
works.
Why can the setting of TEXINPUTS a problem for
context?
Herbert
___________________________________________________________________________________
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:[~2010-10-19 12:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 9:05 itemize Herbert Voss
2010-10-19 9:17 ` itemize luigi scarso
2010-10-19 9:27 ` itemize Hans Hagen
2010-10-19 9:38 ` itemize Herbert Voss
2010-10-19 9:40 ` itemize Khaled Hosny
2010-10-19 9:50 ` itemize Herbert Voss
2010-10-19 10:50 ` itemize Herbert Voss
2010-10-19 11:00 ` itemize luigi scarso
2010-10-19 11:10 ` itemize Herbert Voss
2010-10-19 11:16 ` itemize luigi scarso
2010-10-19 12:01 ` Herbert Voss [this message]
2010-10-19 12:08 ` itemize Taco Hoekwater
-- strict thread matches above, loose matches on Subject: below --
2013-03-04 12:52 itemize Meer, H. van der
2013-03-04 13:19 ` itemize Marco Patzer
2013-03-04 13:34 ` itemize Meer, H. van der
2013-03-04 14:06 ` itemize Marco Patzer
2011-12-18 18:18 itemize Aditya Mahajan
2011-12-18 21:21 ` itemize Hans Hagen
2010-10-20 8:33 itemize Herbert Voss
2010-10-20 8:54 ` itemize Philipp Gesang
2010-10-20 8:59 ` itemize Herbert Voss
2010-01-18 21:56 itemize Hans Hagen
2006-04-07 11:46 itemize Renaud AUBIN
2006-04-08 13:14 ` itemize Hans Hagen
2004-06-16 15:12 itemize, adobekb Thomas A.Schmitz
2004-06-18 17:03 ` itemize Patrick Gundlach
2004-06-19 17:14 ` itemize Willi Egger
2004-06-20 7:57 ` itemize Patrick Gundlach
[not found] <200201212013.VAA02170@smail.let.uu.nl>
2002-01-22 10:16 ` itemize Hans Hagen
2000-01-14 7:54 Itemize Zeljko Vrba
2000-01-14 10:59 ` Itemize Hans Hagen
2000-01-14 14:39 ` Itemize Taco Hoekwater
2000-01-14 13:40 ` Itemize 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=4CBD88B0.7060706@FU-Berlin.DE \
--to=herbert.voss@fu-berlin.de \
--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).