ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Rogers, Michael K" <mroge02@emory.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Local modules not found
Date: Thu, 17 May 2012 13:05:53 +0000	[thread overview]
Message-ID: <F5589D83-2879-42CB-92F0-E5A9E191B153@emory.edu> (raw)

Hi,

I upgraded to the latest beta from the 2011 stable version for the first time.  Now my local modules are not found.  Having searched the wiki and the mailing list, I can find no help.  Any ideas?

Error messages:

\usemodule[homework-fmt] -->
        resolvers       > modules > not found: 'homework-fmt'

\input homework-fmt -->
        ! I can't find file `homework-fmt'.

Here is a snippet from "context --generate"  that might indicate the problem (/Users/mike/Library/texmf contains my tex modules :

resolvers       | methods | resolver: method=generators, how=uri, scheme=file, argument=/Users/mike/Library/texmf
resolvers       | expansions | scanning path '/Users/mike/Library/texmf', branch '/Users/mike/Library/texmf'
resolvers       | expansions | 266 files found on 20 directories with 58 uppercase remappings
resolvers       | resolving |
resolvers       | resolving | not saving runtime tree '/Users/mike/Library/texmf'

Thanks!

Michael

[Background: I started learning ConTeXt last winter using the 2011 TeXLive version and TeXShop (I've a Mac).  Now the semester is over, I'm trying to update to a more recent ConTeXt.  First I got TeXLive 2012 pre-release, but TeXShop still used last year's ConTeXt.  So I followed the wiki instructions for getting the latest beta.  Eventually I found a directory name was different and now TeXShop uses the latest beta.  The latest beta is in a separate directory tree from TeXLive, which I set up 6 months ago or so from instructions on the wiki for running Mark IV.]

________________________________

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).
___________________________________________________________________________________
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:[~2012-05-17 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 13:05 Rogers, Michael K [this message]
2012-05-17 13:09 ` Marco Pessotto
2012-05-17 14:15   ` Rogers, Michael K
2012-05-17 15:59 ` Mojca Miklavec

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=F5589D83-2879-42CB-92F0-E5A9E191B153@emory.edu \
    --to=mroge02@emory.edu \
    --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).