ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tim Li <timli2013@outlook.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Is the lastest beta broken?
Date: Sun, 14 Apr 2013 05:05:20 +0000	[thread overview]
Message-ID: <BLU152-W24C6936C656B65C90B9531A9C30@phx.gbl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4227 bytes --]

Today, I updated my ConTeXt standalone but after that, if I ran `context' it would give these message: d:\>context
contextmtxrun          | forcing cache reload
resolvers       | resolving | looking for 'texmfcnf.lua' on given path 'C:/Users/peng/texmf/web2c' from specification 'home:texmf/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/bin/' from specification 'selfautoloc:'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/' from specification 'selfautodir:'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/texmf-mswin/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on given path 'D:/context/tex/../texmf-local/web2c' from specification 'selfautoparent:/../texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on weird path 'D:/context/tex/' from specification 'selfautoparent:'
resolvers       | resolving | looking for 'texmfcnf.lua' on given path 'D:/context/tex/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on given path 'D:/context/tex/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on given path 'D:/context/tex/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c'
resolvers       | resolving | looking for 'texmfcnf.lua' on given path 'D:/context/tex/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c'
resolvers       | resolving |
resolvers       | resolving | warning: no lua configuration files found
resolvers       | resolving | no texmf paths are defined (using TEXMF)
resolvers       | resolving |
mtxrun          | the resolver databases are not present or outdated
resolvers       | resolving | using suffix based filetype 'lua'
resolvers       | resolving | remembering file 'mtx-context.lua'
resolvers       | resolving | using suffix based filetype 'lua'
resolvers       | resolving | remembering file 'mtx-contexts.lua'
resolvers       | resolving | remembered file 'mtx-context.lua'
resolvers       | resolving | using suffix based filetype 'lua'
resolvers       | resolving | remembering file 'mtx-t-context.lua'
resolvers       | resolving | using suffix based filetype 'lua'
resolvers       | resolving | remembering file 'mtx-t-contexts.lua'
resolvers       | resolving | remembered file 'mtx-t-context.lua'
resolvers       | resolving | using suffix based filetype 'lua'
resolvers       | resolving | remembering file 'context.lua'
mtxrun          | unknown script 'context.lua' or 'mtx-context.lua'
d:\> Is this suggesting that the new beta is broken? If not, how can I solve this problem? I like ConTeXt very much! 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 5683 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2013-04-14  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14  5:05 Tim Li [this message]
2013-04-14  8:42 ` Hans Hagen

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=BLU152-W24C6936C656B65C90B9531A9C30@phx.gbl \
    --to=timli2013@outlook.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).