From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[2]: ConTeXt modules
Date: Wed, 30 May 2001 19:59:25 +0200 [thread overview]
Message-ID: <3721245.20010530195925@bigfoot.com> (raw)
In-Reply-To: <3.0.6.32.20010530141848.01453290@server-1>
Wednesday, May 30, 2001 Hans Hagen wrote:
HH> 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?
HH> In order to prevent name clashes, the m- x- s- and p- prefixes are reserved
HH> for myself and pragma folks. I can support u-* for user modules, but we
HH> need to make sure that users make unique names. If needed i can put those
HH> public user things into a separate archive. So, how about a u- prefix?
Sounds sensible to me. I just wanted to submit the "speech"
module, unless you plan to "stream-line" it in the core
distribution (btw, I finally have it working properly, so if you
want the final version, I can post it, here or privately).
HH> Also, *styles* never are modules, except from those in the standard
HH> distribution (the s- and x- ones that i make here). User styles are
HH> environments and are loaded with \environment
Yes. Also please see my other post about the
environment/product/component stuff.
--
Giuseppe "Oblomov" Bilotta
prev parent reply other threads:[~2001-05-30 17:59 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
2001-05-30 17:59 ` Giuseppe Bilotta [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=3721245.20010530195925@bigfoot.com \
--to=bourbaki@bigfoot.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).