ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: ConTeXt modules
Date: Wed, 30 May 2001 14:18:48 +0200	[thread overview]
Message-ID: <3.0.6.32.20010530141848.01453290@server-1> (raw)
In-Reply-To: <1748547700.20010529220031@bigfoot.com>

At 10:00 PM 5/29/01 +0200, Giuseppe Bilotta wrote:
>Hello, this is mostly directed to Hans.
>
>Is there a convention for the naming of modules, when creating new
>ones? Since I'm quite sure not everybody is interested in the
>thing I'm doing, and yet I'd like to distribute them as modules,
>how should I name them?

In order to prevent name clashes, the m- x- s- and p- prefixes are reserved
for myself and pragma folks. I can support u-* for user modules, but we
need to make sure that users make unique names. If needed i can put those
public user things into a separate archive. So, how about a u- prefix? 

Also, *styles* never are modules, except from those in the standard
distribution (the s- and x- ones that i make here). User styles are
environments and are loaded with \environment  

Also, when writing modules, make sure that you use existing keywords in a
consistent way, use soem Capitals in the names of macros, and use only
documented interfaces (in case of doubt: ask!). Later i will provide
scripts for normalizing files. 

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
-------------------------------------------------------------------------


  reply	other threads:[~2001-05-30 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 20:00 Giuseppe Bilotta
2001-05-30 12:18 ` Hans Hagen [this message]
2001-05-30 17:59   ` Re[2]: " Giuseppe Bilotta

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=3.0.6.32.20010530141848.01453290@server-1 \
    --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).