On Tuesday 05 October 2010 11:02 PM, David Rogers wrote:

"texexec" gives MkII; "context" gives MkIV. I think this may need to be documented somewhere easier to find for those new to ConTeXt.

Thank you for that. When I do context first I get, again among other output, the following at the head and tail of output respectively: --- MTXrun | warning: engine mismatch (luv:This is LuaTeX, Version beta-0.60.2-2010071218 (TeX Live 2010) (rev 3736) <> bin:This is LuaTeX, Version beta-0.63.0-2010090921), forcing remake ---snip--- .../2010/texmf-dist/scripts/context/lua/mtx-context.lua:985: attempt to call upvalue 'make_mkiv_format' (a nil value) --- Moreover, context first | grep -i Mk again gives the tail-end output: --- .../2010/texmf-dist/scripts/context/lua/mtx-context.lua:985: attempt to call upvalue 'make_mkiv_format' (a nil value) --- Can this be ignored or is it a cause for concern? If the latter, how can it be fixed? Thank you. Chandra

On 10/5/2010 1:07 PM, Florian Wobbe wrote:

This is the result of the broken TeXLive 2010 installation. It should have worked out of the box before your failed update attempt. Try again with a clean TeXLive 2010 or install minimals.

This is the second trap I fell into by following the instructions in the manuals: all that rsync stuff jazzed up my TeXLive 2010 installation and I had to reinstall. This bad advice is found on the "Running Mark IV" page on the wiki. Of course, I wanted to run MkIV and ended up spending another hour reinstalling TeXLive to get it back. On my desktop machine I have both TeXLive (for Cygwin) and ConTeXt minimals (for Windows) installed, my notebook has only TeXLive. I am no longer tempted to update any of these, even if I prefer to stay current. As a newbie, I wanted to try out the Concrete Roman font ... but abandoned that quest when it looked like I was going to have to tinker with the internals again. I am now staying firmly on the "end user" side of the ConTeXt fence. Tom.

On 10/5/2010 2:06 PM, Aditya Mahajan wrote:

Using the font should be as easy as

\usemodule[simplefonts] \setupmainfont[Concrete Roman]

! Undefined control sequence. <recently read> \setupmainfront l.3 \setupmainfont [Concrete Roman] ? I spent quite some time yesterday trying to find out (A) if the font is actually installed (I think it is), and (B) what its name might be (I thought it might be "cmuconcrete" -- it isn't). But the same manuals that proved helpful before advised me as a beginner to stay away from fonts or I could get into trouble. I was and am ... and now I'm sticking with all the defaults. Tom.

On 10/5/2010 2:30 PM, luigi scarso wrote:

I remember \setmainfont and not \setupmainfont

That seems to work. Thank you very much. I appreciate your help. Tom.

On Wed, Oct 6, 2010 at 04:07, R (Chandra) Chandrasekhar wrote:

If I wanted to fix my broken TeXLive, should I just re-install ConTeXt from the TeXLive 2010 DVD or should I do a full re-install of the full scheme?

You have two options: a) finish what you started b) reinstall In case of reinstall, it should be enough if you reinstall context and luatex, I guess that can be done with: tlmgr install --reinstall context luatex You will have some leftovers (extra files), but that should in general not be a problem. (You can try to delete (= first move to some other place) texmf-dist/tex/context before reinstalling if tmlgr won't complain too much about missing files that cannot be removed.) If something goes very bad, you can of course always reinstall everything, but if the above works, there's no reason to worry. If you want to finish what you have just started, you need to also sync mtxrun and fetch texmfcnf.lua from minimals and fix it according to TL structure. (That's slightly more non-trivial.) I almost forgot about that file when I said that one should also update mtxrun. Mojca

On Wed, Oct 6, 2010 at 19:19, R (Chandra) Chandrasekhar wrote:

ConTeXt  ver: 2010.07.30 11:35 MKII  fmt: 2010.10.5  int: english/english

system          : cont-new loaded (/localhost/texlive/2010/texmf-dist/tex/context/base/cont-new.tex

FatalError      : Your format does not match the base files!

Usually running (for the whole system) sudo fmtutil-sys --all or fmtutil-sys --all or texexec --make en should help. If not, try to figure out where an additional copy of cont-en.fmt resides, delete it and run any of commands above. You don't need to reinstall anything.

Wanting to have both context minimals and TeXLive 2010--modified only by tlmgr--coexisting, I tried to install the minimals in a directory called

~/local-context

using the following commands:

rsync -av rsync://contextgarden.net/minimals/current/context/current/ \  ~/local-context/

rsync -av --include 'mtxrun' --include 'luatools' \  rsync://contextgarden.net/minimals/current/bin/context/linux-64/bin/ \        ~/local-context/bin/

No, no, no. You could go to http://minimals.contextgarden.net/setup/ and follow those instructions. You can do: cd ~/local-context rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . ./first-setup.sh and then use . ~/local-context/tex/setuptex when you want to switch. The method you use won't "simply work" for various reasons.

If there is a complete error-free algorithm/script in future for making TeXLive 2010 and the context-minmals coexist independently I will appreciate knowing about it.

The are able to coexist independently as long as you don't clone the instructions from wiki (now already removed fro wiki).

Meanwhile, it looks like I need to reinstall TeXLive 2010 afresh.

No, you just need to remake the formats. Mojca

On 6-10-2010 8:46, Tom Maynard wrote:

The information on this page http://wiki.contextgarden.net/Configure_TeXnicCenter_for_ConTeXt ends up invoking MkII (i.e. texexec). Is there any information on the equivalent MkIV configuration?

The commands given above are:

(A) Path to the compiler...

C:\ConTeXt\usr\local\context\tex\setuptex.bat& C:\ConTeXt\usr\local\context\tex\texmf-mswin\bin\texmfstart

(B) Command line arguments...

texexec.rb --bat --nonstop --pdf --interface=nl --color "%bm"

I believe that the 'texmfstart' and obviously the 'texexec.rb' will have to change (at least). To what? There is no 'context.rb' on my system.

Any help is appreciated.

mkiv? just context yourfile.tex mkiv does not need ruby as it uses luatex itself as (lua) script engine texmfstart is replaced by mtxrun ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Wed, Oct 6, 2010 at 20:46, Tom Maynard wrote:

...

The information on this page http://wiki.contextgarden.net/Configure_TeXnicCenter_for_ConTeXt ends up invoking MkII (i.e. texexec).  Is there any information on the equivalent MkIV configuration?

The commands given above are:

(A) Path to the compiler...

C:\ConTeXt\usr\local\context\tex\setuptex.bat & C:\ConTeXt\usr\local\context\tex\texmf-mswin\bin\texmfstart

(B) Command line arguments...

texexec.rb --bat --nonstop --pdf --interface=nl --color "%bm"

I believe that the 'texmfstart' and obviously the 'texexec.rb' will have to change (at least).  To what?  There is no 'context.rb' on my system.

Any help is appreciated.

It should probably be OK to set compiler to    C:\ConTeXt\usr\local\context\tex\texmf-mswin\bin\context.exe and arguments to ... hmmm,    --nonstop "%bm" --batchmode run without stopping and don't show messages on

On Wed, Oct 6, 2010 at 9:30 PM, Mojca Miklavec wrote: the console --nonstopmode run without stopping

do you need anything else? --pdf and --color are not needed, I have no idea what --bat does; --bat(man) ? For catwoman

-- luigi

On Wednesday 06 October 2010 11:39 PM, Mojca Miklavec wrote:

On Wed, Oct 6, 2010 at 19:19, R (Chandra) Chandrasekhar wrote:

...

ConTeXt ver: 2010.07.30 11:35 MKII fmt: 2010.10.5 int: english/english

system : cont-new loaded (/localhost/texlive/2010/texmf-dist/tex/context/base/cont-new.tex

FatalError : Your format does not match the base files!

Usually running (for the whole system) sudo fmtutil-sys --all or fmtutil-sys --all or texexec --make en should help. If not, try to figure out where an additional copy of cont-en.fmt resides, delete it and run any of commands above.

You don't need to reinstall anything.

Thank you very much. I did the following: 1. Deleted /localhost/texlive/2010/texmf-var/web2c/xetex/cont-en.fmt ./localhost/texlive/2010/texmf-var/web2c/pdftex/cont-en.fmt 2. Ran fmtutil-sys --all 3. Ran texexec --make en All three steps were needed to get both texexec and context working under TeXLive 2010, and now they do. I have verified by looking at generator field of the PDF file properties.

...

Wanting to have both context minimals and TeXLive 2010--modified only by tlmgr--coexisting, I tried to install the minimals in a directory called

~/local-context

using the following commands:

rsync -av rsync://contextgarden.net/minimals/current/context/current/ \ ~/local-context/

rsync -av --include 'mtxrun' --include 'luatools' \ rsync://contextgarden.net/minimals/current/bin/context/linux-64/bin/ \ ~/local-context/bin/

No, no, no. You could go to http://minimals.contextgarden.net/setup/ and follow those instructions.

Thanks for the link.

You can do: cd ~/local-context rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . ./first-setup.sh and then use . ~/local-context/tex/setuptex when you want to switch. The method you use won't "simply work" for various reasons.

...

If there is a complete error-free algorithm/script in future for making TeXLive 2010 and the context-minmals coexist independently I will appreciate knowing about it.

The are able to coexist independently as long as you don't clone the instructions from wiki (now already removed fro wiki).

...

Meanwhile, it looks like I need to reinstall TeXLive 2010 afresh.

No, you just need to remake the formats.

Mojca

Thank you. Chandra

On Tuesday 05 October 2010 11:15 PM, Florian Wobbe wrote:

I used to update TeXLive 2009 successfully with this method, however I ran into the same error when updating TeXLive 2010. As I did not succeed and could not figure out what caused the error I installed minimals without problems. I suggest you install minimals and point the environment variable OSFONTDIR to your TeXLive tree. This adds only about 200MiB to your disk which is rather neglectable compared to the 2.7GiB of a full TeXLive.

I trust that minimals is what I was updating using with rsync and that it is a cut-down version of the ConTeXt distribution that came with TeXLive 2010. Can I put minimals in $TEXMFHOME which is ~/texmf on my system? That seems to be the place where I can keep stuff newer than TeXLive 2010 without conflict. Can minimals function standalone, though, or will I run into mismatches with TeXLive 2010 again? Also, should OSFONTDIR then point to /usr/local/texlive/2010/texmf/ or to something else?

see http://archive.contextgarden.net/message/20101003.061025.ee87f16c.en.html

Thank you. That email was very helpful. Chandra

On 6-10-2010 9:32, Florian Wobbe wrote:

No, you clobbered your TeXLive distro with the current context beta.

normally that would work out ok given that you delete the old base path and also update luatex binaries, but in 2010 it also demands installing texmfcnf.lua as we no longer use texmf.cnf ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Wed, Oct 6, 2010 at 04:02, R (Chandra) Chandrasekhar wrote:

Can I put minimals in $TEXMFHOME which is ~/texmf on my system? That seems to be the place where I can keep stuff newer than TeXLive 2010 without conflict. Can minimals function standalone, though, or will I run into mismatches with TeXLive 2010 again?

That would be a bad idea. First of all - it's much better to install minimals in parallel. If nothing else, if the latest beta breaks, you will still have a working ConTeXt somewhere. But the main reason is that even if you put the latest ConTeXt into TEXMFHOME, you will still experience problems because: - you need the latest luatex - you need the latest mtxrun script - you need to fix texmfcnf.lua (you could do this without breaking the rest of TL though, but you need to do it manually)

Also, should OSFONTDIR then point to /usr/local/texlive/2010/texmf/ or to something else?

This is usually the folder where your system stores fonts. LuaTeX can already find all the fonts in TEXMF tree, you probably want to tell LuaTeX where all the other fonts are. If you don't need any other fonts but those that are shipped with TL, you may leave this variable empty. Mojca

On Wednesday 06 October 2010 12:33 AM, Mojca Miklavec wrote:

Thank you. I was searching for that piece of information on the wiki, but wasn't able to find the right page. I have removed it now to avoid any further confusion. The instructions were necessary back in 2009 since ConTeXt was seriously broken in TL, but now that ConTeXt at least runs, even if outdated, it might be better to have a parallel installation of minimals, or to update it via tlmgr.

Are you saying that re-installing ConTeXt from the TeXLive 2010 DVD and periodically running tlmgr update --self --all should take care of any context updates? In any case, if I wished to use the minimals installation, can I set it up in my TEXMFHOME directory at ~/texmf by modifying the rsync target so: rsync -av rsync://contextgarden.net/minimals/current/context/current/ ~/texmf/ rsync -av rsync://contextgarden.net/minimals/current/bin/luatex/linux-64/bin/luatex ~/texmf Or would I be better advised to stay with what TeXLive 2010 provides for now?

In the meantime, since you probably need to fix the installation at least, you may try to run rsync -av --include 'mtxrun' --include 'luatools' \ rsync://contextgarden.net/minimals/current/bin/context/linux-64/bin/ \ /usr/local/texlive/2010/bin/x86-64-linux/ in order to at least get the two scripts back in a working condition.

I did that and got the same error as reported previously.

In a very short time (probably at the first current release of ConTeXt) one should be able to update it in TeX Live in a clean way.

This seems the most convenient solution for me. When is this likely to happen and will a tlmgr update be all that I need then? Thank you. Chandra