but is texmfcnf.lua loaded? (--verbose)
Sure. Both for root and the normal user.
ok, another attempt .. new beta
Version 2008.05.27 16:31 happily generates the file database and
compiles both english and dutch formats! Also, it sticks to the proper
cache location I defined in
On Wed, May 28, 2008 at 6:39 PM, Oliver Buerschaper wrote:
P.S. Can you put that context stub back into the minimals?
It's only missing in the scripts/context/stubs/unix/ folder, in
scripts/context/stubs/mswin/ it is present :)
Mojca
___
dev-context
Mojca Miklavec wrote:
On Wed, May 28, 2008 at 6:39 PM, Oliver Buerschaper wrote:
P.S. Can you put that context stub back into the minimals?
It's only missing in the scripts/context/stubs/unix/ folder, in
scripts/context/stubs/mswin/ it is present :)
well, i copy a non existing unix stub
well, i copy a non existing unix stub into the zip
is this one ok?
#!/bin/sh
mtxrun --script context $@
Perfect. It's exactly the one that used to be present in the beta
2008.05.24 20:06 (both in the binaries as well as the unix stubs
directories). I was wondering why you removed it at
Another question: what part of the LuaTeX chain is responsible for
locating the configuration files? Is it the scripts mtxrun.lua and
luatools.lua or the binary texlua itself? You mentioned something
about luatools only but now that Hans uploaded the entire beta ...
this is done in
What I mean is this: in the full path /usr/texbin/luatex, texbin
can be a symlink to a different directory and that will be followed,
but if luatex itself is a symlink to a file in a different
directory,
that will not be noticed.
I think this should be just fine for the moment ...
Extended
Oliver Buerschaper wrote:
Another question: what part of the LuaTeX chain is responsible for
locating the configuration files? Is it the scripts mtxrun.lua and
luatools.lua or the binary texlua itself? You mentioned something
about luatools only but now that Hans uploaded the entire
Who's lud?
Lua :-)
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
Oliver Buerschaper wrote:
What I mean is this: in the full path /usr/texbin/luatex, texbin
can be a symlink to a different directory and that will be followed,
but if luatex itself is a symlink to a file in a different
directory,
that will not be noticed.
I think this should be just fine for
Martin Schröder wrote:
2008/5/23 Hans Hagen [EMAIL PROTECTED]:
sure, but it depends on tmp being cleaned up too; afaik /tmp and c:/temp
are only cleaned up periodically e.g. when one runs out of space so it's
a kind of indication of 'may be cleaned up'
Many Unixes clear /tmp at bootup. Even
Hi Taco,
This new release is available now.
I've just had the chance to test this new release and got mixed
results ... the 2008.05.21 minimal distribution (LuaTeX only) now sits
in
/usr/local/context/2008-05-21
and there's a symbolic link
/usr/texbin -
Oliver Buerschaper wrote:
Obviously, the problem is the symbolic link because LuaTeX tries and
finds argv[0] in $PATH but doesn't resolve /usr/texbin to its actual
location on disk. It's clear that in this situation there can't be any
difference between the distribution-independent
Hans Hagen wrote:
Oliver Buerschaper wrote:
Obviously, the problem is the symbolic link because LuaTeX tries and
finds argv[0] in $PATH but doesn't resolve /usr/texbin to its actual
location on disk. It's clear that in this situation there can't be
any difference between the
Taco Hoekwater wrote:
The chosen method has a few small flaws in bordercases that will
be corrected eventually (in a new luatex release) but it seems
to work well enough for now
Before Oliver tells me I am being vague again: ;-)
What I mean is this: in the full path
Hi again,
(replying to myself)
Taco Hoekwater wrote:
Oliver, I have emailed you a patched version of luatools.lua. Can
you try to make sure that it works for you as well? (It should, but ...)
Hans is just finished uploading a new beta that has two fixes in
this area:
* there was a bug in
Unrelated - how exactly do I set TEXMFCACHE to be in texmf-cache
alongside other texmf trees?
I have tried (I know that this cannot work):
TEXMFCACHE = '$TEXROOT/texmf-cache',
but TEXROOT is probably unknown anyway
I forgot to finish the sentence:
with this setting I get
luatools
Mojca Miklavec wrote:
Here I have the cnf file under
/usr/local/gwTeX/texmf.cnf
huh, in the root of the tree? is that also true for upcoming versions?
i'm not sure if we should support all variants of trees and maybe gwtex
assumes an env var to be set?
Hans
On Fri, May 23, 2008 at 9:34 AM, Hans Hagen wrote:
Mojca Miklavec wrote:
in the path bases variant, you cannot use TEXOS and TEXROOT since they don't
exist; you can try TEXMFCACHE=/tmp
I know, but I do not want the cache to go to /tmp. It's still nice to
be able to reuse it from time to time.
Mojca Miklavec wrote:
On Fri, May 23, 2008 at 9:31 AM, Hans Hagen wrote:
Mojca Miklavec wrote:
Here I have the cnf file under
/usr/local/gwTeX/texmf.cnf
huh, in the root of the tree? is that also true for upcoming versions? i'm
not sure if we should support all variants of trees and
few? afaik all windows and linux systems -)
No :-) I have to insist like one year ago, *no* Linux machine I have
an account on does set TMP or TEMP (using various distributions). Maybe
that's a shell problem, I don't know, but on any case you can't rely on it.
anyhow, taco and i decided
weird because what then is the purpose of that variable
But if there is no such variable, what's the point of looking for its
purpose? :-) I suppose that on Unix, functions like mkstemp have to be
preferred for truly temporary directories.
Arthur
Arthur Reutenauer wrote:
weird because what then is the purpose of that variable
But if there is no such variable, what's the point of looking for its
purpose? :-) I suppose that on Unix, functions like mkstemp have to be
preferred for truly temporary directories.
sure, but it depends
Norbert Preining wrote:
On Mi, 21 Mai 2008, Taco Hoekwater wrote:
that the ConTeXt shipping with TeX Live should be regarded as the
official stable release ...
We have not added mkiv to texlive. If it is included now, then that
is thanks to Norbert's packaging.
No I didn't add anything to
Mojca Miklavec wrote:
On Fri, May 23, 2008 at 7:45 PM, Norbert Preining wrote:
But AFAIS, the whole context could in fact be omitted. As far as I see
*everyone* using context also uses his home-grown installation etc ;-)
- ConTeXt on MikTeX is completely/absolutely broken
- TeX Live is
2008/5/23 Arthur Reutenauer [EMAIL PROTECTED]:
To /tmp, but there is no $TMP or $TEMP defined anywhere.
weird, maybe they use some apple name, like $WASTEBIN or $THRASH
We already had that discussion: very few systems actually set TMP or
TEMP (the first public releases of Mark IV used to
On Wed, May 21, 2008 at 7:27 PM, Arthur Reutenauer wrote:
So, assuming /opt/tex/texmf-linux/bin, it attempts the following
directories, in this order:
[/opt/tex/texmf]/web2c% two parents up
[/opt/tex/texmf-linux]/texmf/web2c% one parent up
Taco Hoekwater wrote:
Please note this implementation logic is not set in stone yet. We
preferred to start as simple as possible, but extensions may
be needed. (currently we have a works for me system). Keep in
mind that if your installation is really outlandish, you can just
set TEXMFCNF in
Duncan Hothersall wrote:
only run the setuptex script in the shell in which you want to run
ConTeXt. These environment variables aren't meant to be set globally
(again, AFAIK), they are meant to be set for the session. To me this is
what makes the minimals highly portable and easy to
Oliver Buerschaper wrote:
I was referring to
setuptex.sh
All scripts starting with setuptex have the same functionality:
they set up all the needed environment variables
I have seen the following, that only differ per platform:
setuptex,setuptex.sh % unix bash shell
Oliver Buerschaper wrote:
However, think of someone who has never heard of ConTeXt before but
has been persuaded by a friend or colleague to give it a try. Perhaps
they've been given a template document for a thesis to start from. If
this person has a Mac they'll probably want to download
Taco Hoekwater wrote:
Taco Hoekwater wrote:
So, assuming /opt/tex/texmf-linux/bin, it attempts the following
directories, in this order:
[/opt/tex]/texmf/web2c% two parents up
[/opt/tex/texmf-linux]/texmf/web2c% one parent up
[/opt/tex]/texmf-local/web2c
So, assuming /opt/tex/texmf-linux/bin, it attempts the following
directories, in this order:
[/opt/tex/texmf]/web2c% two parents up
[/opt/tex/texmf-linux]/texmf/web2c% one parent up
[/opt/tex]/texmf-local/web2c
Arthur Reutenauer wrote:
So, assuming /opt/tex/texmf-linux/bin, it attempts the following
directories, in this order:
[/opt/tex/texmf]/web2c% two parents up
[/opt/tex/texmf-linux]/texmf/web2c% one parent up
[/opt/tex]/texmf-local/web2c
well, you need to set the path i assume -)
Yes, sure :-) But it's much easier to control than all the variables
set by setuptex. Now I can switch between the minimals and TeX Live by
simply changing my PATH. Great!
By the way, the rsync minimals have been updated, so it also works
with
Arthur Reutenauer wrote:
well, you need to set the path i assume -)
Yes, sure :-) But it's much easier to control than all the variables
set by setuptex. Now I can switch between the minimals and TeX Live by
simply changing my PATH. Great!
By the way, the rsync minimals have been
hm, but that not much more keying than calling setuptex -)
No, it's very different, because it's reversible: once you've sourced
setuptex, there's no going back unless you unset dozens of variables.
Up to now I had to use diiferent shells for TeX Live and the Minimals.
Hans and I are extending context in this area right now, so any
current answer will likely be outdated before much longer.
So, a little bit of extra patience is required still.
I see. It's just that literally everything about ConTeXt is changing
on a daily basis and almost every current
Oliver Buerschaper wrote:
Hans and I are extending context in this area right now, so any
current answer will likely be outdated before much longer.
So, a little bit of extra patience is required still.
I see. It's just that literally everything about ConTeXt is changing on
a daily basis
Hello Taco,
I see. It's just that literally everything about ConTeXt is
changing on a daily basis and almost every current answer about
just any topic seems to be outdated within a fortnight.
Well, what else do you expect from code that is in active development?
Sorry, but this rant
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
51 matches
Mail list logo
