On Fri, Jun 12, 2009 at 07:25, Peter Münster wrote:
On Fri, 12 Jun 2009, Mojca Miklavec wrote:
I left TEXMFCACHE variable as an excuse for not adding texmfcnf.lua to
the distribution. (Though in theory it's still not needed, you just
need to regenerate the database since LuaTeX doesn't know
Mojca Miklavec wrote:
But I'm asking myself, how SELFAUTOPARENT works:
luatex is here: /opt/context/tex/texmf-linux-64/bin/luatex
So it seems, that SELFAUTOPARENT is /opt/context/tex
Yes.
But I would have guessed that it's /opt/context/tex/texmf-linux-64 ...
No, that's SELFAUTODIR.
When loading minimals with a shell script it appears that setuptex
takes arguments from the calling shell script:
script called as script --current contains:
...
source ./setuptex
...
This result in the following error message:
mktexlsr: Done.
The argument
Hans van der Meer wrote:
When loading minimals with a shell script it appears that setuptex takes
arguments from the calling shell script:
script called as script --current contains:
source ./setuptex
This result in the following error message:
mktexlsr: Done.
The argument
On Thu, 11 Jun 2009, Hans van der Meer wrote:
When loading minimals with a shell script it appears that setuptex takes
arguments from the calling shell script:
Indeed. 2 solutions:
- treat or save your arguments before calling setuptex, for example:
ARG1=$1
ARG2=$2
shift $#
source
On Thu, Jun 11, 2009 at 12:26, Hans van der Meer wrote:
When loading minimals with a shell script it appears that setuptex takes
arguments from the calling shell script:
script called as script --current contains:
...
source ./setuptex
...
This result in the following error message:
- or setuptex should be rather an executable, that prints out the
environment to apply, then one would do something like this:
eval `setuptex`
(cleaner solution, but some work to do and all minimal-users must change
their habits...)
I theory adjusting PATH should do, but it's a nice
On Thu, 11 Jun 2009, Mojca Miklavec wrote:
- or setuptex should be rather an executable, that prints out the
environment to apply, then one would do something like this:
eval `setuptex`
(cleaner solution, but some work to do and all minimal-users must change
their habits...)
I
On Thu, Jun 11, 2009 at 23:25, Peter Münster wrote:
On Thu, 11 Jun 2009, Mojca Miklavec wrote:
- or setuptex should be rather an executable, that prints out the
environment to apply, then one would do something like this:
eval `setuptex`
(cleaner solution, but some work to do and all
On Fri, 12 Jun 2009, Mojca Miklavec wrote:
I left TEXMFCACHE variable as an excuse for not adding texmfcnf.lua to
the distribution. (Though in theory it's still not needed, you just
need to regenerate the database since LuaTeX doesn't know about the
location of your old cache.)
I have
10 matches
Mail list logo
