From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@let.uu.nl
Subject: Re: How to add your own modules?
Date: Mon, 21 Oct 2002 12:07:45 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20021021120640.02b5cc90@server-1> (raw)
In-Reply-To: <20021021073224.GC545@swordfish>
At 01:32 AM 10/21/2002 -0600, Matt Gushee wrote:
>Thank you all for the suggestions.
>
>On Fri, Oct 18, 2002 at 10:53:38PM +0200, Henning Hraban Ramm wrote:
>
> > Not really.
> > Your own modules should go into (texmf-var or so)/tex/context/user
> > and you should name them t-somewhat.tex (t for "third-party module").
> > Then you can address them with \usemodule[somewhat] (without t-).
>
>Is that all you need to do? I have tried that and it's not working. Do
>you need to somehow "register" your module with the system or perhaps
>generate a format file before using it?
maybe you need to run mktexlsr so that the file is known to the kpse file
searching lib
didn't change the layout at all, just used different fonts and colors.
>Would that be an appropriate task for an environment?
or just in your document, preceding \starttext
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-10-21 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 20:36 Matt Gushee
2002-10-18 20:53 ` Henning Hraban Ramm
2002-10-21 7:32 ` Matt Gushee
2002-10-21 10:07 ` Hans Hagen [this message]
2002-10-18 21:28 ` [NTG-context] " Giuseppe Bilotta
2002-10-20 16:54 ` 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=5.1.0.14.1.20021021120640.02b5cc90@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@let.uu.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).