From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reading modules broken?
Date: Sat, 07 Jun 2014 19:08:46 +0200 [thread overview]
Message-ID: <5393471E.4020802@wxs.nl> (raw)
In-Reply-To: <659FBBDF-3289-4997-B6EB-9D274C21B7DF@gmail.com>
On 6/7/2014 12:52 PM, Wolfgang Schuster wrote:
>
> 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?
It is actually an old one (that can go, i had some v files on my machine
.. collected examples).
In file-mod.lua we have commands.usemodules, and we can extend that to
support the case where a user has provided some prefix (prefixing
prevents clashes with files elsewhere in the tex tree)
...
if status then
-- ok, don't change
elseif find(truename,"%-") and usemodule(truename) then
-- assume a user namespace
report_modules("using user prefixed file %a",truename)
status = 1
elseif not permit_unprefixed then
-- forget about it
elseif usemodule(truename) then
report_modules("using unprefixed file %a",truename)
status = 1
else
status = 0
end
...
Btw, in the case of hvdm, an option would have been:
\enabledirectives[modules.permitunprefixed]
I'm somewhat surprised that the issues show up now as that code is not
that young.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 17:08 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
2014-06-07 17:08 ` Hans Hagen [this message]
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=5393471E.4020802@wxs.nl \
--to=pragma@wxs.nl \
--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).