From: Hans Hagen <pragma@wxs.nl>
To: hajtmar@gyza.cz, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How well do ConTeXt (lua)module for other users?
Date: Wed, 20 Jul 2011 11:41:36 +0200 [thread overview]
Message-ID: <4E26A2D0.8020601@wxs.nl> (raw)
In-Reply-To: <4E268683.5050400@gyza.cz>
On 20-7-2011 9:40, Jaroslav Hajtmar wrote:
> Thanx Wolfgang.
>
> Is there a solid practice of naming modules? I noticed that the names
> appear modules including introductory letters "p" or "t" ... You also
> used the name p-test.lua. What does it mean? How to correctly name the
> module, or what other elements should it include?
p is for private i.e. never part of the distribution
t is for third party i.e. can be installed on demand
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-07-20 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 12:27 Jaroslav Hajtmar
2011-07-19 12:31 ` luigi scarso
2011-07-19 12:39 ` Wolfgang Schuster
2011-07-19 14:26 ` Jaroslav Hajtmar
2011-07-19 15:06 ` Wolfgang Schuster
2011-07-20 7:40 ` Jaroslav Hajtmar
2011-07-20 9:41 ` Hans Hagen [this message]
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=4E26A2D0.8020601@wxs.nl \
--to=pragma@wxs.nl \
--cc=hajtmar@gyza.cz \
--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).