ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wei-Wei Guo <wwguocn@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeXLive 2008 + ConTeXt problems (on Gentoo Linux)
Date: Wed, 15 Apr 2009 08:30:08 +0800	[thread overview]
Message-ID: <49E52A90.6030105@gmail.com> (raw)
In-Reply-To: <200904141827.04323.matija.suklje@rutka.net>

Hi Matija,

You need to set TEXMFCNF, TEXMFCACHE, and OSFONTDIR in your system environment,
for example in /etc/env.d/98texlive.


Best wishes,
Wei-Wei


Matija Šuklje 写道:
> Hullo,
> 
> it's been a while since I used ConTeXt (I simply didn't have to write any 
> documents), but now that I upgraded to TeXLive 2008 I noticed that ConTeXt is 
> giving me gripes.
> 
> 'context test.tex' produces:
> MtxRun | error unable to identify cnf file
> MtxRun | error unable to identify cnf file
> MtxRun | no cnf files found (TEXMFCNF may not be set/known)
> MtxRun | unknown script: context
> 
> 'texexec test.tex' actually produces a PDF.
> 
> 'luatex test.tex' starts asking questions:
> This is LuaTeX, Version snapshot-0.30.3-2009041418 (Web2C 7.5.7)
> (test.tex
> ! Undefined control sequence.
> l.1 \starttext
> 
> ?
> 
> ...and later on produces a completely messed up PDF
> 
> 
> 'luatools --generate' produces:
> LuaTools | error unable to identify cnf file
> LuaTools | error unable to identify cnf file
> LuaTools | no cnf files found (TEXMFCNF may not be set/known)
> LuaTools |
> LuaTools | runtime: 0.046 seconds
> 
> 
> I'm sure there's a step I missed in the upgrade, but I have no idea what. I've 
> already tried a few things from the Wiki, which I think resulted in 'texexec' 
> actually working, but the rest is still foo.
> 
> Does anyone have any idea what I'm doing wrong?
> 
> 
> Cheers,
> Matija Šuklje
> 
> 
> ------------------------------------------------------------------------
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / 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
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / 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
___________________________________________________________________________________

  parent reply	other threads:[~2009-04-15  0:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 16:27 Matija Šuklje
2009-04-14 17:48 ` Hans Hagen
2009-04-14 20:29   ` Matija Šuklje
2009-04-14 20:47     ` Hans Hagen
2009-04-15  0:30 ` Wei-Wei Guo [this message]
2009-04-15  3:07   ` Matija Šuklje
2009-04-15  3:33     ` Wei-Wei Guo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49E52A90.6030105@gmail.com \
    --to=wwguocn@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).