From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reading modules broken?
Date: Sat, 7 Jun 2014 12:52:46 +0200 [thread overview]
Message-ID: <659FBBDF-3289-4997-B6EB-9D274C21B7DF@gmail.com> (raw)
In-Reply-To: <539229FD.8040405@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]
Am 06.06.2014 um 22:52 schrieb Hans Hagen <pragma@wxs.nl>:
> On 6/6/2014 9:35 PM, Meer, H. van der wrote:
>> My modules are not read anymore, allthough Context thinks it does. This must have been the case for some time. I ran a test with an older version which demonstrates that the change in behaviour must have occurred after january second.
>> Minimal example follows.
>>
>> Hans van der Meer
>>
>> Module code in file module-test is:
>> \writestatus{HVDM}{Module has been read}
>> \endinput
>>
>> Test code in file moduletest.tex is:
>> \usemodule[module-test]
>> \starttext
>> module testing look into the log.
>> \stoptext
>
> modules have names like
>
> m-
> x-
> s-
> p-
> u-
What’s the meaning of the new “v” prefix for modules?
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1490 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-06-07 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 19:35 Meer, H. van der
2014-06-06 20:52 ` Hans Hagen
2014-06-07 10:11 ` Meer, H. van der
2014-06-07 10:52 ` Wolfgang Schuster [this message]
2014-06-07 17:08 ` Hans Hagen
2014-06-07 12:40 ` Andreas Schneider
2014-06-07 13:05 ` Meer, H. van der
2014-06-07 16:47 ` Hans Hagen
2014-06-07 17:09 ` Hans Hagen
2014-06-15 9:38 ` Schmitz Thomas A.
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=659FBBDF-3289-4997-B6EB-9D274C21B7DF@gmail.com \
--to=schuster.wolfgang@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).