On Feb 13, 2008 3:59 PM, Johannes Graumann wrote:
>
> Mojca Miklavec wrote:
>
> > On Feb 13, 2008 3:43 PM, Johannes Graumann wrote:
> >> Johannes Graumann wrote:
> >> > Thanks for the hint. Different error now: how to remedy
> >> > 'LuaTools | running command:
> >> > luatex --ini --lua="cont-en.luc"
> >> > "/home/balin/context/tex//texmf-context/tex/context/base/cont-en.tex"
> >> > \\dump
> >> > (/home/balin/context/tex//texmf-context/tex/context/base/cont-en.tex !
> >> > I can't find file `context.tex'. l.16 \input context.tex'
> >> >
> >>
> >> It's there ...
> >>
> >> find -iname context.tex
> >> ./context/tex/texmf-context/tex/context/base/context.tex
> >>
> >> .but not found?
> >
> > Hmmm ... I have thought that this only happens on windows (as it works
> > fine here). The file name database is apparently broken (see double
> > '//'), but no idea why. And no idea why it doesn't work on your
> > computer whili it does on mine.
> >
> > How did you call setuptex? What does
> >    export | grep TEX
> > return?
> Nothing, whether I run setuptex or no ... I must be missing something in
> setting up the minimal ...

but running setuptex means: [dot] setuptex. Else it has no effect.

Here's the whole procedure once more:

rsync -av rsync://contextgarden.net/minimals/setup/osx-intel/first-setup.sh .
./first-setup.sh
# then, you might need to skip a bunch of currently broken greek patterns)
cd tex
# note the dot !!!
. setuptex
# generate luatex format - only because its autogeneration
# is broken at the moment
texexec --make --lua en

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to