INstall minimal context system.

older
continuous numbering of subsection

John R. Culleton

25 Jun 2006 25 Jun '06

5:27 p.m.

I downloaded the justtex.zip and the context-linux.zip files into a work directory /usr/local/cont and unzipped them. Then I cd to the tex directory under that work directory. I made the the setuptex file executable and executed it with no apparent effect. Then I changed the path to point to /usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed the new path. I ran texexec --make --alone and it seemed to be successful. Ran mktexlsr again. Then I ran a test program in another directory. It could not find cont-en.fmt. In fact this file or anything similar to this file does not exist in this tree, although it existed in my previous tetex tree and exists in my texlive tree. How do I create and/or download this file? -- John Culleton

Show replies by date

Idris Samawi Hamid

25 Jun 25 Jun

6:22 p.m.

On Sun, 25 Jun 2006 17:27:41 -0600, John R. Culleton wrote:

...

I downloaded the justtex.zip and the context-linux.zip files into a work directory /usr/local/cont and unzipped them. Then I cd to the tex directory under that work directory. I made the the setuptex file executable and executed it with no apparent effect. Then I changed the path to point to /usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed the new path. I ran texexec --make --alone and it seemed to be successful.

Just a guess: since you used the --alone switch, is there a path to the current directory from which you invoked texexec --make --alone Without the --alone switch the fmt file should go into \texmf-linux\web2c or \texmf-linux\web2c\pdfetex, depending on your texexec.ini setup. (I use Windows but the principle should be the same) Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Aditya Mahajan

9:16 p.m.

On Sun, 25 Jun 2006, Idris Samawi Hamid wrote:

...

On Sun, 25 Jun 2006 17:27:41 -0600, John R. Culleton wrote:

...
I downloaded the justtex.zip and the context-linux.zip files into a work directory /usr/local/cont and unzipped them. Then I cd to the tex directory under that work directory. I made the the setuptex file executable and executed it with no apparent effect. Then I changed the path to point to /usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed the new path. I ran texexec --make --alone and it seemed to be successful.

setuptex just sets some system variables (TEXMF, TEXMFMAIN, TEXMFLOCAL and so on) and modifies the PATH, so you will not get any immediate feedback on whether it ran correctly or not. Depending on your shell you may have to "source setuptex path-to-setuptex" or just "setuptex path-to-setuptex" As a quick check to see if everything went fine, do "echo $TEXMF" before and after sourcing setuptex.

...

Just a guess: since you used the --alone switch, is there a path to the current directory from which you invoked texexec --make --alone

Without the --alone switch the fmt file should go into \texmf-linux\web2c or \texmf-linux\web2c\pdfetex, depending on your texexec.ini setup.

IIRC, the new (ruby) texexec does not read texexec.ini. One possibility is that $TEXMFLOCAL is not set (as you did not run setuptex) so texexec did not know where to place the format files. This also happens with Miktex and texexec creates a directory pdfetex in the current directory and dumps the format files there. You can try moving the fmt files to /usr/loca/cont/tex/texmf-local/web2c/pdfetex Aditya

Taco Hoekwater

26 Jun 26 Jun

1:16 a.m.

Aditya Mahajan wrote:

...

setuptex just sets some system variables (TEXMF, TEXMFMAIN, TEXMFLOCAL and so on) and modifies the PATH, so you will not get any immediate feedback on whether it ran correctly or not. Depending on your shell you may have to "source setuptex path-to-setuptex" or just "setuptex

most importantly, "source setuptex" or just "setuptex" will not have the desired effect. Taco

Mojca Miklavec

3:49 a.m.

On 6/26/06, John R. Culleton wrote:

...

I downloaded the justtex.zip and the context-linux.zip files into a work directory /usr/local/cont and unzipped them. Then I cd to the tex directory under that work directory. I made the the setuptex file executable and executed it with no apparent effect.

You have to execute . setuptex ie. [dot] setuptex in that specific folder and than tex will work in that shell only. I've put something equivalent to cd /usr/local/cont/tex . setuptex cd into my .bashrc. I'm not sure that that's the proper and most elegant solution, but it was the only one that I found to be working. (An alternative would surely be a "smart copy" of contents of setuptex to .bashrc.)

...

Then I changed the path to point to /usr/local/cont/tex/texmf-linux/bin and ran mktexlsr.

If setuptex was executed properly, it should already be in your PATH. If not, other environmental variables needed to run TeX properly are not set either, so the formats will not be copied where they were supposed to be.

...

It followed the new path. I ran texexec --make --alone and it seemed to be successful. Ran mktexlsr again. Then I ran a test program in another directory. It could not find cont-en.fmt. In fact this file or anything similar to this file does not exist in this tree, although it existed in my previous tetex tree and exists in my texlive tree.

How do I create and/or download this file?

You can't download it. texexec --make --all (or --make --alone, it doesn't really matter I guess) should create it and copy it to the proper destination. If it didn't, ConTeXt won't work properly either since the rest of the needed environmental variables are not set properly. Mojca

6595

Age (days ago)

6596

Last active (days ago)

List overview

Download

4 comments

5 participants

participants (5)

Aditya Mahajan
Idris Samawi Hamid
John R. Culleton
Mojca Miklavec
Taco Hoekwater