ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: I can't change startitemize[n]--> startitemize[1]
Date: Thu, 23 Jul 2009 17:11:52 +0200	[thread overview]
Message-ID: <fe8d59da0907230811t72c4ecb6iac31c949983ab637@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0907231101220.6655@ybpnyubfg.ybpnyqbznva>


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

On Thu, Jul 23, 2009 at 5:05 PM, Aditya Mahajan <adityam@umich.edu> wrote:

> On Thu, 23 Jul 2009, luigi scarso wrote:
>
>  On Thu, Jul 23, 2009 at 4:37 PM, Hans Hagen <pragma@wxs.nl> wrote:
>>
>>  Xan wrote:
>>>
>>>  Really, I did not know that. It's a messy thing that we could not define
>>>
>>>> what we like ;-)
>>>>
>>>>
>>> it's the nature of a tex macro package; ok, i can add some strict testing
>>> for in in mkiv but even then it might just be that someone who knows th
>>> einternals (like wolfgang or wolfgang or wolfgang) wants to overload
>>> something built in by something better
>>>
>>>  why not discipline ?
>>
>> I mean something like
>> 0) context macro are ok
>> 1) \usemodule[foo] are ok (no collision with macros in 0)
>> 2) define your macros inside
>> \startPrivate[namespace]
>> ...
>> \stopPrivate
>> 3) explicit  redefinition of macros in 0,1
>>
>> by 3) should be no collision between 0,1,2
>>
>

>
> I think an easier thing to do will be to follow latex's style of
> \newcommand and \renewcommand. That is, all \definecommands should check if
> the macro is previously defined or not. If it is defined, issue a warning or
> an error. And maybe have some hook to disable the warning/error for those
> who know what they are doing.
>
yes, it's equivalent




-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2413 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-07-23 15:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 12:06 Xan
2009-07-23 12:45 ` Wolfgang Schuster
2009-07-23 14:05   ` Hans Hagen
2009-07-23 14:33     ` Xan
2009-07-23 14:37       ` Hans Hagen
2009-07-23 14:48         ` luigi scarso
2009-07-23 14:58           ` Wolfgang Schuster
2009-07-23 15:05             ` luigi scarso
2009-07-23 15:10               ` Wolfgang Schuster
2009-07-23 15:16                 ` luigi scarso
2009-07-23 15:26                   ` luigi scarso
2009-07-23 15:33                   ` Wolfgang Schuster
2009-07-23 15:46                     ` luigi scarso
2009-07-23 15:05           ` Aditya Mahajan
2009-07-23 15:11             ` luigi scarso [this message]
2009-07-23 15:16             ` Wolfgang Schuster
2009-07-23 15:52               ` Aditya Mahajan
2009-07-23 15:57                 ` luigi scarso
2009-07-23 16:04                 ` Hans Hagen
2009-07-23 15:42         ` Xan

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=fe8d59da0907230811t72c4ecb6iac31c949983ab637@mail.gmail.com \
    --to=luigi.scarso@gmail.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).