On Mo, 19 Mai 2008, Mojca Miklavec wrote:
Any ideas if getting rid of dependency on environmental variables is doable?
And please also of that *stupid* user-specific luatex-cache. There must
be a way to run-time merge a system-wide luatex-cache with a
luatex-cache only for the user files.
like
Mojca Miklavec wrote:
On Mon, May 19, 2008 at 9:03 AM, Taco Hoekwater wrote:
Norbert Preining wrote:
Well not surprising ... there is NO context script anywhere in the
distribution!
Am I missing something?
The script is:
scripts/context/lua/mtx-context.lua
If mtxrun cannot find it,
Norbert Preining wrote:
Hi everyone,
aehmmm, looks nice, but
# let us see how the context wrapper looks like:
$ cat /usr/bin/context
#!/bin/sh
mtxrun --script context $@
# now see what mtxrun does ...
$ mtxrun --script context foobar
MtxRun | unknown script: context
$
Oliver Buerschaper wrote:
Any ideas if getting rid of dependency on environmental variables
is doable?
I agree it would be great if mtxrun could call/do setuptex on itself
if needed.
At the moment for me it would be enough to know where exactly LuaTeX
looks for configuration
Norbert Preining wrote:
On Mo, 19 Mai 2008, Mojca Miklavec wrote:
Any ideas if getting rid of dependency on environmental variables is doable?
And please also of that *stupid* user-specific luatex-cache. There must
be a way to run-time merge a system-wide luatex-cache with a
luatex-cache
Hi Hans,
On Mo, 19 Mai 2008, Hans Hagen wrote:
Again, you should definitely implement some level of global setup
possibility!!!
you mean shared for users?
Yes.
keep in mind that i hav eno experience with multi user systems (ok, long
What we actually need, and that is the same for TeX
What we actually need, and that is the same for TeX Live and for all
distributions (at least inmy imagination), is:
- one (or several) system wide luatex cache thingies
- one per user (if the user wants to)
- a way to update the cache for specific trees only
(luatools --system-only ...)
-
I really wonder how (if at all) LuaTeX is going to work on MikTeX ...
:) ConTeXt is broken there already, and ConTeXt is the only tool that
really benefits from LuaTeX (apart from some of your tools on TL). The
new search capabilities are likely to break the MikTeX's auto-install
Mojca Miklavec wrote:
What we actually need, and that is the same for TeX Live and for all
distributions (at least inmy imagination), is:
- one (or several) system wide luatex cache thingies
- one per user (if the user wants to)
- a way to update the cache for specific trees only
(luatools
On Mo, 19 Mai 2008, Hans Hagen wrote:
for that to happen we need to define what system is and what is user in
a pretty consistent and cross platform way (and not in the tetex n*m
permutations way)
system: TEXMFDIST TEXMFMAIN TEXMFLOCAL TEXMFSYSCONFIG TEXMFSYSVAR
user: TEXMFHOME TEXMFVAR
On Mo, 19 Mai 2008, Hans Hagen wrote:
system: TEXMFDIST TEXMFMAIN TEXMFLOCAL TEXMFSYSCONFIG TEXMFSYSVAR
i suppose that this is the order in $TEXMF in tex live then
No no no, that was the order in which the stuff came to my mind!!!
just wondering ... how is a system wide update taking place
At the moment for me it would be enough to know where exactly
LuaTeX looks for configuration information (path file name) and
which files take precedence over others in the case of
conflicts ... my current understanding is:
1. Environment variables
2. setuptex.tmf
no, this one is
12 matches
Mail list logo
