ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Module Namespaces
Date: Mon, 29 Nov 2010 19:52:47 +0100	[thread overview]
Message-ID: <20101129185247.GA27584@aides> (raw)
In-Reply-To: <1669D1AA-6C08-41CB-B964-700330D5A921@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1567 bytes --]

Hi all,

On 2010-11-29 <19:17:00>, Wolfgang Schuster wrote:
> 
> Am 18.11.2010 um 19:33 schrieb luigi scarso:
> 
> > I just want to register my namespace(s) to be sure to avoid conflicts
> > not only for modules but also for lua code
> 
> Good idea and it’s not a problem to reserve „lscarso“ for you but i ask
> myself which of these tables (luat-ini.lua) are available for users:
> 
> userdata      = userdata      or { } -- might be used
> thirddata     = thirddata     or { } -- might be used
> moduledata    = moduledata    or { } -- might be used
> documentdata  = documentdata  or { } -- might be used
> parametersets = parametersets or { } -- experimental
> 
> document      = document      or { }

If I may add to this question: I am using “job.variables” as kind
of base for my private use area (not for modules, though) -- bad
habit or valid alternative?

Thanks, Philipp

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

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

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

  reply	other threads:[~2010-11-29 18:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  9:13 luigi scarso
2010-11-18  9:26 ` Philipp Gesang
2010-11-18 18:08 ` Wolfgang Schuster
2010-11-18 18:33   ` luigi scarso
2010-11-29 18:17     ` Wolfgang Schuster
2010-11-29 18:52       ` Philipp Gesang [this message]
2010-11-29 19:10         ` luigi scarso
2010-12-06 16:50         ` Hans Hagen
2010-12-08 13:17           ` Philipp Gesang
2010-12-06 16:48       ` Hans Hagen
2010-11-29 18:19     ` Wolfgang Schuster
2010-11-18 21:03   ` Aditya Mahajan
2010-11-18 21:19     ` luigi scarso
2010-11-18 21:45       ` Hans Hagen
2010-11-18 21:48         ` Aditya Mahajan
2010-11-18 21:52           ` Hans Hagen
2010-11-18 21:59           ` luigi scarso

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=20101129185247.GA27584@aides \
    --to=pgesang@ix.urz.uni-heidelberg.de \
    --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).