From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: "j. van den hoff" <veedeehjay@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Loading modules
Date: Tue, 23 Dec 2014 14:29:08 +0100 [thread overview]
Message-ID: <DA3A7E1D-7644-451E-A945-39781795187D@gmail.com> (raw)
In-Reply-To: <op.xrboggh0p7eajd@muck.fritz.box>
[-- Attachment #1.1: Type: text/plain, Size: 1890 bytes --]
> Am 23.12.2014 um 14:15 schrieb j. van den hoff <veedeehjay@googlemail.com>:
>
> On Mon, 22 Dec 2014 22:35:43 +0100, Wolfgang Schuster <schuster.wolfgang@gmail.com <mailto:schuster.wolfgang@gmail.com>> wrote:
>
>>
>>> Am 22.12.2014 um 00:12 schrieb j. van den hoff <veedeehjay@googlemail.com>:
>>>
>>> OK, I've just installed the standalone version and adjusted my search path. now the very same document does no longer compile. I get the error:
>>>
>>> 8<---------------------------
>>> ! Undefined control sequence
>>>
>>> <recently read> \doctitle
>>>
>>> l.106 \doctitle
>>> 8<---------------------------
>>> where `doctitle' is defined in a small bare bones module (co-existing in the same dir as the doc) for setting up a title page. I guess I'm hitting some (context-) searchpath issue here that already is taken care of in the texlive distro? any help'd be appreciated.
>>
>> I guess you load the file with your definitions with the \usemodule command.
>
> correct.
>
>>
>> There has been a change a while ago and context expects now a prefix
>> when you load a module (e.g. p-<myfile>.tex) and when you add now the
>> prefix to your file context will be able to load it. Another solution is to add
>>
>> \enabledirectives[modules.permitunprefixed]
>>
>> before the \usemodule command in your document, the command
>> above tells context to also look for modules without a prefix as last resort.
>
> yes, this one did the trick. thanks a lot. regarding the prefix handling/recognition, I don't
> quite get it (_what_ is considered a prefix, e.g. is there a canonical prefix separator etc. or where do I define
> the prefix?). I'll try to hunt for it on contextgarden. if you do have a pointer, though,
> that'd be nice.
http://wiki.contextgarden.net/Modules#Usage <http://wiki.contextgarden.net/Modules#Usage>
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 9730 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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-12-23 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 18:31 access to system fonts under MacOSX j. van den hoff
2014-12-20 22:26 ` Pablo Rodriguez
2014-12-21 10:51 ` j. van den hoff
2014-12-21 16:01 ` Pablo Rodriguez
2014-12-21 13:31 ` j. van den hoff
2014-12-21 16:20 ` Pablo Rodriguez
2014-12-21 17:37 ` j. van den hoff
2014-12-21 18:22 ` Pablo Rodriguez
2014-12-21 20:24 ` j. van den hoff
2014-12-21 21:39 ` Wolfgang Schuster
2014-12-21 21:45 ` j. van den hoff
2014-12-21 21:56 ` Wolfgang Schuster
2014-12-21 22:23 ` j. van den hoff
2014-12-21 23:12 ` j. van den hoff
2014-12-22 6:09 ` Pablo Rodriguez
2014-12-23 13:19 ` j. van den hoff
2014-12-22 21:35 ` Loading modules (was: access to system fonts under MacOSX) Wolfgang Schuster
2014-12-23 13:15 ` j. van den hoff
2014-12-23 13:29 ` Wolfgang Schuster [this message]
2014-12-23 13:29 ` j. van den hoff
2014-12-23 13:38 ` Loading modules Wolfgang Schuster
2014-12-21 22:17 ` access to system fonts under MacOSX Pablo Rodriguez
2014-12-21 22:22 ` j. van den hoff
2014-12-21 22:11 ` Pablo Rodriguez
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=DA3A7E1D-7644-451E-A945-39781795187D@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=veedeehjay@googlemail.com \
/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).